[Bug 676611] Re: [IDT 92HD71B7X] ALSA test tone not correctly played back
And now, after entering bug, two reboots later, all is well. Sigh. -- [IDT 92HD71B7X] ALSA test tone not correctly played back https://bugs.launchpad.net/bugs/676611 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 676611] Re: [IDT 92HD71B7X] ALSA test tone not correctly played back
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- [IDT 92HD71B7X] ALSA test tone not correctly played back https://bugs.launchpad.net/bugs/676611 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 676611] [NEW] [IDT 92HD71B7X] ALSA test tone not correctly played back
Public bug reported: Sound was working earlier this morning, had been since 9.04 (?Not sure when I bought this lappie) Stopped working. No idea why. Nothing is muted, all levels are up. No sound. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: alsa-base 1.0.23+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 2.6.35-23.37-generic 2.6.35.7 Uname: Linux 2.6.35-23-generic i686 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pww 30495 F pulseaudio /dev/snd/pcmC0D0p: pww 30495 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdf00 irq 50' Mixer name : 'Nvidia MCP77/78 HDMI' Components : 'HDA:111d76b2,103c30f6,00100302 HDA:11c11040,103c137e,00100200 HDA:10de0006,10de0101,0010' Controls : 25 Simple ctrls : 14 Date: Wed Nov 17 08:05:48 2010 PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SelectedCard: 0 Intel HDA-Intel - HDA Intel SourcePackage: alsa-driver Symptom: audio Title: [IDT 92HD71B7X] ALSA test tone not correctly played back dmi.bios.date: 02/06/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F4 dmi.board.vendor: Compal dmi.board.version: 99.98 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd02/06/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.26:rvnCompal:rn30F4:rvr99.98:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: F.26 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug i386 maverick -- [IDT 92HD71B7X] ALSA test tone not correctly played back https://bugs.launchpad.net/bugs/676611 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 288185] Re: Evolution plain-text email includes formatting "stuff" - should be pure plain text
Can someone explain the status change (from unknown to new)? Just curious. Also curious whether there will be action on this, it continues to be a usability pain. Thanks! -- Evolution plain-text email includes formatting "stuff" - should be pure plain text https://bugs.launchpad.net/bugs/288185 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 566544] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
On Mon, 2010-04-19 at 20:09 +, Pedro Villavicencio wrote: > this looks similar to bug > https://bugzilla.gnome.org/show_bug.cgi?id=596204 ; are you still able > to reproduce the crash? Evolution-alarm-notify crashes have almost always been unpredictable for me, but they almost always follow waking from suspend. I've never been able to get one to occur reliability, but when they occur they tend to come in consistent bunches (get several over a course of days, then not again for weeks/months). -- evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/566544 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 429953] Re: gnome-screensaver-gl-helper crashed with SIGSEGV
*** This bug is a duplicate of bug 429964 *** https://bugs.launchpad.net/bugs/429964 ** This bug has been marked a duplicate of bug 429964 gnome-screensaver-gl-helper crashed with SIGSEGV -- gnome-screensaver-gl-helper crashed with SIGSEGV https://bugs.launchpad.net/bugs/429953 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 429964] Re: gnome-screensaver-gl-helper crashed with SIGSEGV
I've closed this (marked as invalid) since this happened during the Karmic release cycle, has not occurred with production Karmic, and has not occurred with Lucid. The bug just ain't there no more. ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New => Invalid -- gnome-screensaver-gl-helper crashed with SIGSEGV https://bugs.launchpad.net/bugs/429964 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 105868] Re: time "until charged" is wrongly calculated
Folks, there have been no updates or activity on this report for over a year. Does the problem continue to occur, with Karmic (or Lucid, if you are using the beta)? -- time "until charged" is wrongly calculated https://bugs.launchpad.net/bugs/105868 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 321605] Re: sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04
Since a new report has been filed, since others no longer experience this issue, and there have been no updates for 5+ months I am closing this report (marking as invalid). ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Invalid -- sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04 https://bugs.launchpad.net/bugs/321605 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 60243] Re: Does not resume from suspend
There have been no updates or activity on this bug for over a year. Does the behavior still occur under Karmic (or under the Lucid beta)? If so, please run the command apport-collect -p linux 60243 in a terminal window. If anyone is experiencing a similar problem - but not this exact problem - please attempt first to find a bug report that matches the problem you are experiencing; if you find such a report, please attempt to provide any information by the developers, including possibly running "apport- collect -p linux theBugNumber". If you do not find such a report the behavior your are experiencing, please open a new report as described in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies -- Does not resume from suspend https://bugs.launchpad.net/bugs/60243 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 246659] Re: Backuppc no compression when change topdir
Does this problem persist in 9.10 (Karmic) or in the Lucid beta? The RedHat bug report is somewhat confusing as to whether the cpool patch has been released -- Backuppc no compression when change topdir https://bugs.launchpad.net/bugs/246659 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 75497] Re: Asus P4P800 motherboard doesn't suspend
Folks, no new information has been added to this report in almost a year. Could someone please try this with Karmic, or perhaps the Lucid beta? If the bug continue to occur, please run the command apport-collect -p linux 75497 in a terminal window. If anyone is experiencing a similar problem - but not this exact problem - please attempt first to find a bug report that matches the problem you are experiencing; if you find such a report, please attempt to provide any information by the developers, including possibly running "apport- collect -p linux theBugNumber". If you do not find such a report the behavior your are experiencing, please open a new report as described in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies If the behavior no longer occurs or if no new information is provided, I will close this in about two weeks. -- Asus P4P800 motherboard doesn't suspend https://bugs.launchpad.net/bugs/75497 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 78163] Re: cat /proc/acpi/button/lid/LID/state returns closed
Dave, does this behavior still occur under Karmic? (Or under Lucid, if you have been trying the beta?) -- cat /proc/acpi/button/lid/LID/state returns closed https://bugs.launchpad.net/bugs/78163 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 91599] Re: reclose the CD tray if a CD is mounted and fight with gnome for eject key
Didier, are you still experiencing this behavior? Under what release? Thanks! -- reclose the CD tray if a CD is mounted and fight with gnome for eject key https://bugs.launchpad.net/bugs/91599 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 50692] Re: New Sony Vaios hotkeys don't work (fn_key polling)
There was no activity on this bug report for 2+ years, then a couple of recent comments. In all likelihood this should be closed as invalid - I will do that in about 2 weeks unless there are updates with new information. The type of information required: What release are you running? Are all updates applied? Is the sony-laptop module installed (if applicable - it may have been superseded by recent kernel updates)? -- New Sony Vaios hotkeys don't work (fn_key polling) https://bugs.launchpad.net/bugs/50692 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 79504] Re: vbetool crash report
I'm closing this report - marking as invalid - as there has been no activity for almost a year. ** Changed in: vbetool (Ubuntu) Status: Incomplete => Invalid -- vbetool crash report https://bugs.launchpad.net/bugs/79504 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 349985] Re: [Dell Inc. Studio 1535] suspend/resume failure
I no longer have this machine and can no longer test the problem, so I am marking this as invalid and moving on. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- [Dell Inc. Studio 1535] suspend/resume failure https://bugs.launchpad.net/bugs/349985 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Changed status to Invalid: No further problems, all features work (sound, video, etc.), dimness upon resume is an occasional and irreproducible problem. Sometimes it happens, sometimes it doesn't, no pattern. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 476729] Re: Evolution freezes when adding attachement
Folks, I'd like to close this as it is likely the problem has been fixed - please refer to bug# 460710. If you are still experiencing this with Karmic, please make sure that you have all updates applied, then attempt to reproduce the bug using the steps above. If you are no longer experiencing this, please let us know so we can close this report. -- Evolution freezes when adding attachement https://bugs.launchpad.net/bugs/476729 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 43961] Re: Power down after shutdown does not work...
There has been no activity on this bug report for over 60 days, and there was almost a full year between the last two comments. It's probably time to close it once and for all (status is Triaged for Linux (Ubuntu), but just in case If anyone is experiencing this exact problem with Karmic or Lucid, please run the following command: apport-collect -p linux 43961 in a terminal window. If anyone is experiencing a similar problem - but not this exact problem - please attempt first to find a bug report that matches the problem you are experiencing; if you find such a report, please attempt to provide any information by the developers, including possibly running "apport-collect -p linux theBugNumber". If you do not find such a report the behavior your are experiencing, please open a new report as described in https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies Please do NOT attach new information to or otherwise update this report with workarounds or information related to other bugs. I will mark this bug as invalid in two weeks if there are no relevant updates. -- Power down after shutdown does not work... https://bugs.launchpad.net/bugs/43961 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Update: I found the trick for changing brightness on this machine (sigh, let's chalk it up to user error and leave it at that). This means that as of today's updates, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/432230/comments/7 is the correct summary: Suspend works, except for the "via dbus whilst on AC", resume works, brightness can be restored to proper levels. The original problem hasn't recurred for months. Everything else seems fine, so we can: 1) Close this report, and open a new one to track the brightness/dimness problem, 2) Close this report, and ignore the brightness/dimness problem, or 3) Leave this open to track the brightness/dimness problem. I'm sort of tempted by #2 (less work), though #1 would be more complete. Thoughts? -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Almost. I cannot restore the brightness. The dimness after resume is permanent until I reboot. It is now that way upon any and all resumes, where it used to be that way only when resuming after suspending after being on battery (didn't matter if resume/suspend was on AC/DC, any combo thereof): Go on battery, then suspend on AC or battery, then resume, dim. No way to get bright. Now it is perfectly consistent: Suspend, resume, dim until reboot. Also, I'd quibble with "dbus seems to fail", but that's just a quibble (the machine does not suspend and the test script reports an error; that's an error with the script, expecting it cannot get, or with suspend not happening when it should, but either way it is a clear failure). -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Hmph, submitted too quickly. Please note that with the dimness the way it is, suspend is effectively useless, because the screen is too dim upon resume for anything but the most pressing brief work. Please consider this when assigning an importance level to the bug. -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Good news: Recent updates (since Thursday March 18th) have restored proper GDM behavior. I can suspend and resume, return to my session, and move between VTs. I've run $ sudo bash /usr/share/checkbox/scripts/suspend_test --full | tee ~/sustest.full and have attached sustest.full. The only thing that appears to have failed is the first test, suspending from dbus. I've not had the "no network on resume" for a while. That's + However, I do have the diminished screen brightness upon resume problem. That's - Given that lsusb, lspci, etc., were all attached when the original report was filed, should I rerun and reattach them or is them some other debugging information that would be more useful? ** Attachment added: "Output of /usr/share/checkbox/scripts/suspend_test --full" http://launchpadlibrarian.net/41462411/sustest.full -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Oh, forgot one thing: On resume under Lucid, networking is often - but not always - disabled. I have to option-click the network-manager icon and enable it explicitly. Unplugging and replugging the Ethernet cable doesn't do it, nor does turning the radio on and off. (I usually have the radio off.) Under Jaunty and Karmic, wired networking was always fine. (Wireless had unreproducible flakiness, but worked most of the time.) (By option-click I mean the "other" mouse button; I use a left-handed mouse, so it's left click, but not your left click :->) -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
The "suspend-test --full" test is unavailable to me because of the GDM restart issue: A terminal window within gnome disappears when GDM restarts, and as of now, for whatever reason, I can no longer get a console prompt. After rebooting the machine a few minutes ago, the first several times I tried getting to VT1, not only did I get a blank screen on the VT, but GDM restarted - I was back at gnome login. After letting the gnome session "sit" for a while (long enough for the screensaver to come on, I can at least attempt to navigate away and back to VT7 and gnome without losing that session, but other VTs are still unavailable to me. FWIW, suspend-test results visible before losing my gnome session were: suspend for 20s via dbus while on AC: failed. suspend for 20s via dbus while off AC: succeeded, but resume got me back to a gnome login session. At this point, guidance is required. Not being able to get to a console is a serious handicap, and the problem may not be kernel resume but GDM or display related. Without the console, the standard debugging techniques seem out of reach. All suggestions for a way forward are welcome. -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Suspend on this machine has always been flaky*, but with Lucid the problems are perfectly reproducible. The major problem with Lucid is that suspend-and-resume restarts my GDM session. I've tested with two users logged in (regular and test) and after resume, I cannot delete the test user because the system thinks the test user is still logged in. Yet here I am back at the login console. How to reproduce: Boot machine Login, get a gnome session going Suspend by closing lid, choosing suspend from gnome's 'power button' menu, pm-suspend, etc. Resume by pressing the Fn key or opening the lid Presented with login prompt Therefore, this is a resume failure. I've had no flashing caps-lock, been looking for that for a while. This cycle worked with Intrepid and Karmic, though it had its flakiness (Occasionally, display would be dimmed, if resuming on power after suspending on battery; required reboot to fix. Occasionally, would not resume and power button was disabled, had to remove battery and unplug to "free" the machine, then power-up.) The reboot with no_console_suspend and setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz sudo pm-suspend trick produced nothing. No output, same results. I've not tried hibernate yet, I never use it. I am about to run checkbox's suspend-test. -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 348757] Re: [Dell Inc. Studio 1535] suspend/resume failure [non-free: fglrx]
On Sat, 2010-03-13 at 20:32 +, Jeremy Foshee wrote: > This bug report was marked as Triaged a while ago but has not had any > updated comments for quite some time. Please let us know if this issue > remains in the current Ubuntu release, I no longer have the affected machine and so am unable to test with the new release. Please mark this as closed (I would do it myself but have been unable to login to Launchpad for sometime now - an effect of being an edge user?). Thanks. -- [Dell Inc. Studio 1535] suspend/resume failure [non-free: fglrx] https://bugs.launchpad.net/bugs/348757 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 84898] Re: After resume, video playback is order of magnitude slower than normal
On Sat, 2010-03-13 at 06:52 +, Jeremy Foshee wrote: > This bug report was marked as Triaged a while ago but has not had any > updated comments for quite some time. Please let us know if this issue > remains in the current Ubuntu release, I no longer have the affected machine and so am unable to test with the new release. Please mark this as closed (I would do it myself but have been unable to login to Launchpad for sometime now - an effect of being an edge user?). Thanks. -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 505637] Re: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
Interesting. That crash occurred before I opened update-manager to apply the available upgrades. Once update-manager was started, it was allowed to work to completion (and all upgrades on these machines are manually initiated). Difficult to reproduce, at any rate. -- package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 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 505637] Re: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
** Attachment added: "AptOrdering.txt" http://launchpadlibrarian.net/37684878/AptOrdering.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/37684879/Dependencies.txt ** Attachment added: "Dmesg.txt" http://launchpadlibrarian.net/37684880/Dmesg.txt ** Attachment added: "DpkgTerminalLog.txt" http://launchpadlibrarian.net/37684881/DpkgTerminalLog.txt -- package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 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 505637] [NEW] package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt)
Public bug reported: Binary package hint: gnome-screensaver automatic crash report ProblemType: Package Architecture: i386 Date: Sun Jan 3 10:56:21 2010 DistroRelease: Ubuntu 9.10 ErrorMessage: subprocess new post-removal script killed by signal (Interrupt) Package: gnome-screensaver 2.28.0-0ubuntu3.2 ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: gnome-screensaver Title: package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) Uname: Linux 2.6.31-16-generic i686 ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package gnome-screensaver 2.28.0-0ubuntu3.2 failed to install/upgrade: subprocess new post-removal script killed by signal (Interrupt) https://bugs.launchpad.net/bugs/505637 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 496946] [NEW] Nokia 6085 not recognized; filing as per gnokii instructions
Public bug reported: Binary package hint: gnokii The page http://wiki.gnokii.org/index.php/Security_options says if you own a Nokia and "Model" prints a code similar to RM-146 instead of the commercial name of the phone please report this issue to the gnokii mailing list or to the bug tracker of your distribution showing the version of gnokii, the output of gnokii --identify (the IMEI is not needed), the name of the phone as printed on the box and a link to phone page at http://www.forum.nokia.com/devices/ $ gnokii --identify GNOKII Version 0.6.27 IMEI : XX Manufacturer : Nokia Model: RM-260 Product name : RM-260 Revision : V 26.00 Nokia device page: http://www.forum.nokia.com/devices/6085/ Don't have the box, no name available. FYI, I can get much done with this phone with [global] model = 6510 in my .gnokiirc. Much includes SMS, reading calendar and contacts, etc. Haven't tried writing calendar/contacts yet. ** Affects: gnokii (Ubuntu) Importance: Undecided Status: New -- Nokia 6085 not recognized; filing as per gnokii instructions https://bugs.launchpad.net/bugs/496946 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 460710] Re: Evolution hangs when double-clicking on attachment
Brilliant - had the bug again this morning (had to force-quit evolution), enabled karmic proposed, installed all proposed, tried sending exact same email, same attachment, worked fine this time: great work, fix works as promised. -- Evolution hangs when double-clicking on attachment https://bugs.launchpad.net/bugs/460710 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 476729] Re: Evolution freezes when adding attachement
Is this is a dupe of bug# 460710? -- Evolution freezes when adding attachement https://bugs.launchpad.net/bugs/476729 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 448034] Re: package libpython2.6 2.6.4~rc1-0ubuntu1 failed to install/upgrade: error writing to '': Success
** Attachment added: "AptOrdering.txt" http://launchpadlibrarian.net/33407476/AptOrdering.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33407484/Dependencies.txt ** Attachment added: "Dmesg.gz" http://launchpadlibrarian.net/33407485/Dmesg.gz ** Attachment added: "DpkgTerminalLog.gz" http://launchpadlibrarian.net/33407486/DpkgTerminalLog.gz -- package libpython2.6 2.6.4~rc1-0ubuntu1 failed to install/upgrade: error writing to '': Success https://bugs.launchpad.net/bugs/448034 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 448034] [NEW] package libpython2.6 2.6.4~rc1-0ubuntu1 failed to install/upgrade: error writing to '': Success
Public bug reported: Binary package hint: python2.6 running update manager, crash when attempting authentication (after auth failure) ProblemType: Package Architecture: i386 Date: Sat Oct 10 09:06:53 2009 DistroRelease: Ubuntu 9.10 ErrorMessage: error writing to '': Success NonfreeKernelModules: nvidia Package: libpython2.6 2.6.4~rc1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-13.43-generic SourcePackage: python2.6 Title: package libpython2.6 2.6.4~rc1-0ubuntu1 failed to install/upgrade: error writing to '': Success Uname: Linux 2.6.31-13-generic i686 ** Affects: python2.6 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package libpython2.6 2.6.4~rc1-0ubuntu1 failed to install/upgrade: error writing to '': Success https://bugs.launchpad.net/bugs/448034 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 442986] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
I marked this as invalid for three reasons: 1) it has not happened again "on its own", 2) I was unable to reproduce it with a specific test case (create appt 30 minutes in the future; put computer to sleep for 20 minutes; wake computer - reminder is successfully displayed), and 3) there has been a considerable number of updates since the bug occurred, it's likely it was fixed by recent changes. ** Changed in: evolution (Ubuntu) Status: Incomplete => Invalid -- evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/442986 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 442986] Re: evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch()
Steps to reproduce? Sadly, no. Came back from suspend, it crashed, but have yet to be able to reproduce. Has not happened otherwise. -- evolution-alarm-notify crashed with SIGSEGV in g_main_context_dispatch() https://bugs.launchpad.net/bugs/442986 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 432230] Re: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/31996870/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/31996871/AplayDevices.txt ** Attachment added: "BootDmesg.gz" http://launchpadlibrarian.net/31996872/BootDmesg.gz ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/31996873/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/31996877/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/31996878/Card0.Codecs.codec.1.txt ** Attachment added: "Card0.Codecs.codec.2.txt" http://launchpadlibrarian.net/31996885/Card0.Codecs.codec.2.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/31996888/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/31996889/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/31996890/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/31996891/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/31996892/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/31996893/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/31996894/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/31996895/ProcInterrupts.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/31996896/ProcMaps.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/31996897/ProcModules.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/31996898/ProcStatus.txt ** Attachment added: "ResumeHangLog.txt" http://launchpadlibrarian.net/31996900/ResumeHangLog.txt ** Attachment added: "SleepLog.txt" http://launchpadlibrarian.net/31996903/SleepLog.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/31996904/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/31996905/UdevLog.txt ** Attachment added: "WifiSyslog.gz" http://launchpadlibrarian.net/31996906/WifiSyslog.gz -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 432230] [NEW] [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia]
Public bug reported: automatic report - resume failure ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. The resume processing hung very near the end and will have appeared to have completed normally. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pww2938 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xdf00 irq 34' Mixer name : 'Nvidia MCP78 HDMI' Components : 'HDA:111d76b2,103c30f6,00100302 HDA:11c11040,103c137e,00100200 HDA:10de0006,10de0101,0010' Controls : 36 Simple ctrls : 20 Date: Thu Sep 17 06:16:35 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/share/apport/apportcheckresume Failure: late resume HibernationDevice: RESUME=UUID=cbc16eea-857c-4c9e-ab42-80baf1f550b5 InterpreterPath: /usr/bin/python2.6 MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC NonfreeKernelModules: nvidia Package: linux-image-2.6.31-10-generic 2.6.31-10.34 ProcCmdLine: root=UUID=dbc3c043-6c8a-4e8c-a035-9db6648687d2 ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.31-10.34-generic RelatedPackageVersions: linux-backports-modules-2.6.31-10-generic N/A linux-firmware 1.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: linux Tags: resume suspend resume-late-hang Title: [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] Uname: Linux 2.6.31-10-generic i686 UserGroups: WpaSupplicantLog: dmi.bios.date: 02/06/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30F4 dmi.board.vendor: Compal dmi.board.version: 99.98 dmi.chassis.type: 10 dmi.chassis.vendor: Compal dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.26:bd02/06/2009:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvrF.26:rvnCompal:rn30F4:rvr99.98:cvnCompal:ct10:cvrN/A: dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: F.26 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume resume-late-hang suspend -- [Hewlett-Packard HP Pavilion dv7 Notebook PC] late resume failure [non-free: nvidia] https://bugs.launchpad.net/bugs/432230 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 269012] Re: Sound (Intel HDA9) doesn ’t really work (ALSA0) on Intrepid Ibex alpha- 5
I never did get to that testing, sigh. Amazing how demotivating a workaround can be. At any rate, this problem is gone on my DV7 with Karmic - I let the install replace the conf file and all is well. Marking as fix released. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- Sound (Intel HDA9) doesn’t really work (ALSA0) on Intrepid Ibex alpha-5 https://bugs.launchpad.net/bugs/269012 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 374487] Re: no sound in Ubuntu 9.04 64bit
Folks, this problem disappears on my DV7 with Karmic. When you get a chance, please test with Karmic and mark the bug as fix released if it works for you. -- no sound in Ubuntu 9.04 64bit https://bugs.launchpad.net/bugs/374487 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 321605] Re: sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04
Folks, this problem disappears on my DV7 with Karmic. When you get a chance, please test with Karmic and mark the bug as fix released if it works for you. -- sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04 https://bugs.launchpad.net/bugs/321605 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 355747] Re: Choppy sound on HDA-Intel soundcard
I've marked this as "fix released" since I just installed Karmic and the problem is gone: Sound works fine on my DV7. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- Choppy sound on HDA-Intel soundcard https://bugs.launchpad.net/bugs/355747 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 318637] Re: no sound on HP Pavilion tx2510us
Folks, this problem disappears on my DV7 with Karmic. When you get a chance, please test with Karmic and mark the bug as fix released if it works for you. -- no sound on HP Pavilion tx2510us https://bugs.launchpad.net/bugs/318637 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 246659] Re: Backuppc no compression when change topdir
I'm marking this as confirmed as it meets the definition of a real bug no matter how one looks at it. Not being able to move TopDir is a bug: Many of us have /var on / and have / on a single fast disk, but want our main data on our SAN or RAID array. For example, I have /home on /dev/md0 and set TopDir to /home/backuppc. We can move it, but it isn't supported - not supporting such a crucial feature is a bug. Having hardcoded default paths is a bug. It never ceases to amaze that hardcoded paths continue to make it into production software. I've also added the symlink, hope it eliminates that error. ** Changed in: backuppc (Ubuntu) Status: New => Confirmed -- Backuppc no compression when change topdir https://bugs.launchpad.net/bugs/246659 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 84898]
** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/28798059/Lspci.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/28798056/Dependencies.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/28798055/CurrentDmesg.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898] Re: After resume, video playback is order of magnitude slower than normal
Problem persists wit 06-12 kernel (that was latest I could find for i386 arch). Apport reports coming up. -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/28798062/ProcModules.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/28798054/BootDmesg.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/28798060/ProcCpuinfo.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/28798061/ProcInterrupts.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/28798057/HalComputerInfo.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898] apport-collect data
Architecture: i386 DistroRelease: Ubuntu 9.04 HibernationDevice: RESUME=UUID=bacc4efa-22ee-4743-8c7c-80589337ff4c Lsusb: Bus 001 Device 003: ID 0ace:1215 ZyDAS WLA-54L WiFi Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 26284TU Package: linux-image-2.6.30-999-generic 2.6.30-999.1244801613 PackageArchitecture: i386 ProcCmdLine: root=UUID=29b76f26-472e-40c4-afae-6b0eda7980d7 ro quiet splash acpi=force ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_CA.UTF-8 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 2.6.30-999-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/28772126/ProcInterrupts.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/28772125/ProcCpuinfo.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/28772124/Lspci.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/28772128/ProcModules.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "HalComputerInfo.txt" http://launchpadlibrarian.net/28772123/HalComputerInfo.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/28772122/Dependencies.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/28772120/CurrentDmesg.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898]
** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/28772119/BootDmesg.txt -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 84898] apport-collect data
Architecture: i386 DistroRelease: Ubuntu 9.04 HibernationDevice: RESUME=UUID=bacc4efa-22ee-4743-8c7c-80589337ff4c Lsusb: Bus 001 Device 002: ID 0ace:1215 ZyDAS WLA-54L WiFi Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: IBM 26284TU Package: linux-image-2.6.28-13-generic 2.6.28-13.45 PackageArchitecture: i386 ProcCmdLine: root=UUID=29b76f26-472e-40c4-afae-6b0eda7980d7 ro quiet splash acpi=force ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_CA.UTF-8 ProcVersionSignature: Ubuntu 2.6.28-13.45-generic Uname: Linux 2.6.28-13-generic i686 UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video -- After resume, video playback is order of magnitude slower than normal https://bugs.launchpad.net/bugs/84898 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
Marking this as confirmed since it is still a bug, and a well documented one given the contributions between 05-12 and 06-15. Update: Plugged in camera today. Error -60 (as above), error -1 (as above), errors in dmesg. Found this bug report (how could I have forgotten it! :->), killed gvfs-gphoto2-etc., remounted camera, no errors, able to import photos but had to start f-spot manually. Difference between then and now? Recent system updates must have restored sufficient sanity to unbork the system, though it still does not work as expected. ** Changed in: gvfs (Ubuntu) Status: Invalid => Confirmed -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 269012] Re: Sound (Intel HDA9) doesn ’t really work (ALSA0) on Intrepid Ibex alpha- 5
I can do the testing, but owing to previous commitments, I won't likely be able to get to it until early July. (Yeah, I know it's only about 30 minutes of work, but every 1/2 hour is precious right now.) I've added a reminder to do this around about July 3rd. -- Sound (Intel HDA9) doesn’t really work (ALSA0) on Intrepid Ibex alpha-5 https://bugs.launchpad.net/bugs/269012 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 318637] Re: no sound on HP Pavilion tx2510us
You might want to try a clean installation and the workaround suggested on http://forum.notebookreview.com/showthread.php?t=331172 As root (sudo, su, however you prefer to get there), edit the file /etc/modprobe.d/alsa-base and add this line to the end of the file: options snd-hda-intel enable_msi=1 Then reboot. Please note that recent updates (applied between June 15, when I first did the above, and June 22), caused the file to disappear - its entire contents were copied to /etc/modprobe.d/alsa-base.conf. When this happened, I was back to choppy sound. I restored sound by sudo cp -p /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/alsa-base and rebooting. Refer also to bug# 269012 and bug# 355747, and to https://help.ubuntu.com/community/SoundTroubleshooting/#Having%20sound%20issues%20with%20HP%20dvx%20laptop -- no sound on HP Pavilion tx2510us https://bugs.launchpad.net/bugs/318637 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 321605] Re: sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04
You might want to try a clean installation and the workaround suggested on http://forum.notebookreview.com/showthread.php?t=331172 As root (sudo, su, however you prefer to get there), edit the file /etc/modprobe.d/alsa-base and add this line to the end of the file: options snd-hda-intel enable_msi=1 Then reboot. Please note that recent updates (applied between June 15, when I first did the above, and June 22), caused the file to disappear - its entire contents were copied to /etc/modprobe.d/alsa-base.conf. When this happened, I was back to choppy sound. I restored sound by sudo cp -p /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/alsa-base and rebooting. Refer also to bug# 269012 and bug# 355747, and to https://help.ubuntu.com/community/SoundTroubleshooting/#Having%20sound%20issues%20with%20HP%20dvx%20laptop -- sound cant be heard on HP laptop, I cant reproduct sound, cant hear anything on ubuntu 9.04 https://bugs.launchpad.net/bugs/321605 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 374487] Re: no sound in Ubuntu 9.04 64bit
Please try the workaround suggested on http://forum.notebookreview.com/showthread.php?t=331172 As root (sudo, su, however you prefer to get there), edit the file /etc/modprobe.d/alsa-base and add this line to the end of the file: options snd-hda-intel enable_msi=1 Then reboot. Please note that recent updates (applied between June 15, when I first did the above, and June 22), caused the file to disappear - it's entire contents were copied to /etc/modprobe.d/alsa-base.conf. When this happened, I was back to choppy sound. I restored sound by sudo cp -p /etc/modprobe.d/alsa-base.conf /etc/modprobe.d/alsa-base and rebooting. Refer also to bug# 269012 and bug# 355747, and to https://help.ubuntu.com/community/SoundTroubleshooting/#Having%20sound%20issues%20with%20HP%20dvx%20laptop -- no sound in Ubuntu 9.04 64bit https://bugs.launchpad.net/bugs/374487 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 163772] Re: HP Pavilion dv2000 No sound and No wireless
Closed (marked invalid) due to inactivity. ** Changed in: linux (Ubuntu) Status: New => Invalid -- HP Pavilion dv2000 No sound and No wireless https://bugs.launchpad.net/bugs/163772 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 269012] Re: Sound (Intel HDA9) doesn ’t really work (ALSA0) on Intrepid Ibex alpha- 5
I'm marking this as confirmed based on similar behavior on my dv7 and a workaround that could form the basis for a fix. The workaround is to add the following line to /etc/modprobe.d/alsa-base: options snd-hda-intel enable_msi=1 I write "workaround, not fix", for at least two reasons: 1. The user should not have to do this, and, more importantly, 2. After a recent round of updates, this file disappeared for me, but it's entire contents were copied to /etc/modprobe.d/alsa-base.conf - and the problem returned! When I did "cp -p /etc/modprobe/alsa-base.conf /etc/modprobe/alsa-base" and rebooted, the problem went away, sound was good again. The fix would be to have this option set by default for the dv7 series. This problem is known to the community, refer to these sites: http://forum.notebookreview.com/showthread.php?t=331172 https://help.ubuntu.com/community/SoundTroubleshooting/#Having%20sound%20issues%20with%20HP%20dvx%20laptop Refer to ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- Sound (Intel HDA9) doesn’t really work (ALSA0) on Intrepid Ibex alpha-5 https://bugs.launchpad.net/bugs/269012 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 355747] Re: Choppy sound on HDA-Intel soundcard
I'm marking this as confirmed based on similar behavior on my dv7 and a workaround that could form the basis for a fix. The workaround is to add the following line to /etc/modprobe.d/alsa-base: options snd-hda-intel enable_msi=1 I write "workaround, not fix", for at least two reasons: 1. The user should not have to do this, and, more importantly, 2. After a recent round of updates, this file disappeared for me, but it's entire contents were copied to /etc/modprobe.d/alsa-base.conf - and the problem returned! When I did "cp -p /etc/modprobe/alsa-base.conf /etc/modprobe/alsa-base" and rebooted, the problem went away, sound was good again. In other words, sound was as described in this report, I added that line, sound was good, there were recent upgrades (between June 15 and June 22), sound went bad again, I cp'd the file as described, sound is good. The fix would be to have this option set by default for the dv7 series. This problem is known to the community, refer to these sites: http://forum.notebookreview.com/showthread.php?t=331172 https://help.ubuntu.com/community/SoundTroubleshooting/#Having%20sound%20issues%20with%20HP%20dvx%20laptop Refer also to bug# 269012 - one of these may be a dupe of the other. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- Choppy sound on HDA-Intel soundcard https://bugs.launchpad.net/bugs/355747 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 269012] Re: Sound (Intel HDA9) doesn ’t really work (ALSA0) on Intrepid Ibex alpha- 5
Refer also to bug# 355747 - one may be a dupe of the other. -- Sound (Intel HDA9) doesn’t really work (ALSA0) on Intrepid Ibex alpha-5 https://bugs.launchpad.net/bugs/269012 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 163772] Re: HP Pavilion dv2000 No sound and No wireless
>From reviewing this bug, it seems it should have been closed some time ago due to lack of required inputs. I'm unsure as to why status was changed from incomplete to new late last year. Unless there is a compelling reason to keep this open, I'd suggest closing within the next week or two. -- HP Pavilion dv2000 No sound and No wireless https://bugs.launchpad.net/bugs/163772 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
Leandro, based on previous comments (e.g., around #132, etc.), I'd suggest https://wiki.ubuntu.com/NotificationDesignGuidelines/Comments as a good place for your mockups. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
On Thu, 2009-05-14 at 23:18 +, Sebastien Bacher wrote: > could you install gphoto2 as indicated by the message before and try > again to get the log? I installed the app, tried again, but forgot to get the log. However, the results were worse: Install gphoto2 Connect camera: Error -60, error -1 No default application, no pop-up to choose application Start f-spot, attempt to connect to camera, long delay, then error: unable to access camera, unknown error uninstall gphoto2, libcdk5, repeat: Same result! So installing gphoto2 borked what used to work. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
I performed the sequence described above. For my daughter's account, error message (-60) then gthumb photo import (her default action) is started. For my account, same result as above (error, 2 dialogues); for guest, same (error, 2 dialogues). In all cases, despite error messages and extra dialogues, photo import works fine. I do not believe I made any other changes to the system, but now I am doubting myself. As for the command output you requested, $ gphoto2 --summary The program 'gphoto2' is currently not installed. You can install it by typing: sudo apt-get install gphoto2 bash: gphoto2: command not found The output of gvfs-mount -li is attached. ** Attachment added: "output of gvfs-mount -li" http://launchpadlibrarian.net/26736624/gvfs-mount--li -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
OK, this is bizarre. To test default behavior, I restarted the system, logged in, then issued this command in a terminal: sudo chmod +x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor I did this in order to restore the system to default behavior, disabling the workaround quoted previously in the bug report. Then I rebooted, logged in, and connected the Kodak C533. First pop-up was the "error -60" pop-up. Then, two (2!) "you have connected a camera, do you want to open f-spot" pop-ups appeared. I chose to open f-spot, f-spot started, the second "you have connected a camera" pop-up went away on its own, I dismissed the error pop-up, and f-spot was able to talk to the camera just fine. I then turned the camera off, started a guest session, turned the camera on, and got exactly the same behavior. For whatever reason, it has gone from "doesn't work at all" to "works with bizarre extra dialogue and scary dialogue behavior". The only differences between today and last time I tried this are: a) My daughter was also logged in last time (she had logged in first), and b) the chmod -x, chmod +x steps done to make things work last time and to test this time. When my daughter gets home, I will try this again. This is what we will do: Start the machine. She will log in. She will attempt to connect the camera. She will disconnect the camera. I will log in. I will attempt to connect the camera. I will disconnect the camera. I will log in as guest. I will attempt to connect the camera as guest. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
On Wed, 2009-05-13 at 15:23 +, Sebastien Bacher wrote: > ok interesting, do you run a standard GNOME session? Yes. > how many users are logged? Same result with 1 or 2 users logged in. > do you get the issue in a guest session? The camera is with its owner, at school - I will try this this evening and report back. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
On Wed, 2009-05-13 at 14:03 +, Sebastien Bacher wrote: > What is requested there is extra details, ie "I plug the camera, get a > dialog asking if I want to import photos, I click ok, f-spot opens and > displays the error", is that really hard for you to describe? (Taking a deep breath, counting to ten.) Plug the camera in. Get error -60 (who knows from where - the dialogue pops up) Get error -1 No application is started. Nothing useful happens. Only error messages appear. What used to happen: Camera was recognized, user was asked if they want to import photos or perform some other action. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
On Wed, 2009-05-13 at 12:09 +, Sebastien Bacher wrote: > now back to the issue: > - gvfs does mount the device and locks it indeed Does it? Many/most of us get the -60 error, some of us get the -1 error as well, and many/most of us can do nothing with the camera without taking drastic steps (e.g., killall gvfs-gphoto2, chmod -x gvfs-gphoto2) > - software wanting to use the camera should know about that and > gvfs-mount -u if required, f-spot and gthumb at least does it Really? See previous comment (it don't work). > - if somebody has an issue with a software could you open a bug > against that software explaining what you do and how it fails so > those softwares can be changed to do the right thing? "If somebody has an issue with a software" With all due respect, Sebastien, these are the words of a cubicle-bound coder and not the words of someone interested in assisting anyone other than another developer. Most users - the vast majority who just want their computers to work reliably and as expected - do not have the technical knowledge to make the distinction you describe. They used to plug in their camera, it worked. Now it doesn't. For most users - the vast majority who just want their computers to work reliably and as expected - the "software" in question is Ubuntu. That's what they see. Sure, for debugging purposes this can be refined by triagers or developers who know better, but that requires insight and inside knowledge. This is a valid report. If it is not a GVFS bug, then please, since you know more about the inner goings on of the software involved, please direct it elsewhere. If you need to know something specific to assist you with that, then please ask for it. If the bug as originally reported no longer exists, then please mark this fix released, clarify why this report does not apply, and respectfully request that a new report be opened. Continuing to shut this down as "invalid" is simply a slap in the face to the many people who have tried to contribute to this report. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
On Wed, 2009-05-13 at 12:13 +, Sebastien Bacher wrote: > you might also describe how you use f-spot to get the issue, f-spot- > import which is the default GNOME action has this code > > "# make sure it's not mounted by gvfs, otherwise we can't access the > camera > # (current F-Spot version does not yet understand GIO) > gvfs-mount -u "$udi" || true" > > which works fine here and should lead to no error when importing images We get f-spot to work by killing gvfs-gphoto2 (as per the killall in my previous comment) and marking the appropriate gvfs-gphoto2 script as non-executable. Then f-spot can see the camera. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
OK Sebastien, I'll play this game - for a while. When I open the new bug report, I think I will entitle it "Ubuntu can't mount digital camera showing a window popup message: -60 could not lock the device message". That's pretty descriptive of the problem. Then I'll add the fact that dmesg returns something that looks a awful lot like: usb 1-1: new full speed USB device using ohci_hcd and address 3 usb 1-1: configuration #1 chosen from 1 choice scsi10 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 3 usb-storage: waiting for device to settle before scanning Then I'll mention the fact that if I execute the following two commands, the camera can be used in fspot: sudo killall gvfs-gphoto2-volume-monitor sudo chmod -x /usr/lib/gvfs/gvfs-gphoto2-volume-monitor (Of course, fspot no longer opens automatically, I have to open it manually and manually import the photos, but at least it works. Hey, that's good enough, right?) Then a few more people will add information about the same problem. Then guess what? Deviens, si tu peux! My bug report will get marked as a duplicate of this open, because IT IS THE SAME BUG! Exactement le meme. Oh, by the way, the status you are playing? Tu ne suis pas les regles! The bug status you should be using is "Wontfix". At least that's descriptive. Because whatever you say, this is a valid bug report (it contains sufficient information to describe the behavior, properly characterizes the behavior as inappropriate, and properly characterizes it as a regression. So it is by any stretch of the imagination valid. -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 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 285682] Re: Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message
Whether or not this is a bug depends on expected behavior and nothing else. Any other behavior is at best a workaround. On my daughter's machine, plugging in her Kodak C533 worked fine under Hardy and, if memory serves, under Intrepid. By "worked fine", I mean that the default photo import application opened. This was EXPECTED BEHAVIOR. Now that her machine has been upgraded to Jaunty, this no longer works. She gets two error messages, the -60 and an unknown -1. This IS NOT expected behavior. The fact that there is a workaround is wonderful. For the technical user. For the rest of the world, this is a bug. In fact, it is a REGRESSION. What worked no longer works. Frankly, this is a matter of fact - what worked no longer works - and not opinion - something works differently/better/worse but still works. ** Changed in: gvfs (Ubuntu) Status: Invalid => Confirmed -- Ubuntu 8.10 can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, 2009-04-30 at 17:56 +, mac_v wrote: > > +1 .but the only thing would be to drop beneath in a few seconds * only > when the user is working * but *remain persistent until the users > returns to the system* and starts to work. That seems a good idea. However, there are a couple use cases where it would be wrong to have it on top but the user would not seem to be working. Watching a full screen video, for example. Perhaps "If screen is locked, stay on top until screen is unlocked", then apply default behaviour, "stay on top for time T". This is a cleaner use case, I think, fewer what-ifs and exceptions to manage. > but i think this would probably not be possible at present, right? > probably Karmic? Not even, then, I would think, unless and until those doing the design and coding come to believe that another approach is required. > also whats up with no actions in the notify-osd, rather than using the > fall back alerts, why not use a good looking notify-osd with actions , > when required! My apologies, I don't follow. Do you mean have a button on the semi-transparent notify widget "Do Action A"? If so, yes, I agree. There should likely be three: "Do Action A", "Dismiss" (notification never returns), "Snooze" (notification returns sometime later; a default time could be displayed). -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, 2009-04-30 at 15:49 +, getut wrote: > >The issue of trying to guess when is the best time to interrupt people > > MPT... "never" IS a perfectly valid answer to INTERRUPTING a user. +1, mod parent up, etc. At the risk of seeming like I am in love with my own ideas, this was why I proposed the "semi transparent, always present, one window down" notification widget. It would appear from the top right for system notifications (you should upgrade) and the bottom right for user notifications (you have an IM, email, etc.). The notification would appear above the current window (unless operating fullscreen) but would NOT have focus, then drop beneath after a few seconds. When than window is closed or minimized, the notification would be there, then drop down one again. Repeat as necessary. When all windows are closed/minimized, it would be there, without focus. It would say "click here to learn more" or something like. Or even "click here to take action". It would also always have two other buttons: Snooze and dismiss. To me, this is as good as the persistent icon, since it is persistent, but better since it is always there, until the user takes action. It is better than the current approach, because it is always there, and because it differentiates between system and user notifications. Being semi-transparent and dropping away automatically make it more ignorable. Being present until action is taken make it not-ignorable, but in a far less obnoxious way than popups. Other system notifications (volume changes, network connection changes, etc.) would be ephemeral: Appear, then disappear. No action is required, but sometimes the reminder is nice. There would be defaults for what system and what is user, and these would be determined by the community. Administrators would able to modify the system list (for a machine or group of machines). Users would be able to modify the user list for their account. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Sun, 2009-04-26 at 21:38 +, mac_v wrote: > a bit too harsh there pal... Harsh? Perhaps. But given the comparative levels of user frustration and development intransigence, the frustration is understandable. > asking the devs for an apology, is way out there!!! Absolutely not. At this point, I'm starting to think that a contrite mea culpa is the only way forward. People make mistakes. Most of the time, admitting and accepting and moving on is the best approach. But sometimes, when an error is upheld for so long by the errant party, well, the errant party should apologize. Up to this point, I've tried to confine my responses to pointing out the obvious flaws in the Jaunty approach, to proposing alternatives, and to suggesting how the process for introducing these changes could have perhaps been improved. Not because of any inner saintliness, but because I've spat vinegar a time or two and I've learned the hard way how much it gets done. But the development team response from SABDFL on down has been so poor in this area that I'm starting to think vitriol is all we have left. So, yeah, I think we, the Ubuntu community deserve an apology for how this was introduced, for how it was clung too dogmatically in the face of so much opposition of such quality, and for simple intransigence. I don't think asking for apology is off base at all. pww -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 292450] Re: Broadcom STA/wl driver causes random kernel panics
I just updated my Dell MINI - wireless works against my WPA2 network. Thanks, devs, great work. -- Broadcom STA/wl driver causes random kernel panics https://bugs.launchpad.net/bugs/292450 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 292450] Re: Broadcom STA/wl driver causes random kernel panics
Is bug# 300784 a duplicate of this bug? Should status against the Dell Mini Project be opened here and bug# 300784 duped to this one? I'm pretty sure they are the same problem (same symptoms on my Mini and Studio 1535; this fix fixed the Studio) so we just need to get it into LPIA generally and Dell Mini specifically. -- Broadcom STA/wl driver causes random kernel panics https://bugs.launchpad.net/bugs/292450 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
It occurs to me that notification changes should have been handled in the same way as upstart changes, the availability of ext4. compiz effects, etc. In other words, do the work, enable the capability, but don't turn it on. Not yet. Certainly don't make it the default! Get it going, then invite people to test it. For example, have something like both systems in place: The updates-are-available icon would remain *and* the new sliding black widget would appear - it would say something like "updates are available, as is a new notification system - click here to kick tires". (Obviously, this particular approach is half-baked - I'm just making the suggestion.) It's an oft repeated but seldom fully understood development cliche: Prototype, then throw away the prototype once you know what you are doing. And Ubuntu will best thrive when it properly balances top-down dictates with bottom-up designs. In this case, I think we need more prototyping and more bottom-up/top- down balance. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 292450] Re: Broadcom STA/wl driver causes random kernel panics
This morning I tried looking for a binary suitable for a DELL Mini Netbook but nothing seemed appropriate. $ uname -r 2.6.24-19-lpia Help? Thanks! -- Broadcom STA/wl driver causes random kernel panics https://bugs.launchpad.net/bugs/292450 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, 2009-04-09 at 16:55 +, mac_v wrote: > wouldnt this problem be avoided if there was a reminder, which reminded > me after my work was over, to restart? I thought of this as well, and included a mechanism in my comments on the wiki page - when you click on a system notification, you are presented with three options: * Cancel (addresses the I'm about to reboot and I know about problem, I'll deal with it on my own cases) * Do now * Do later (with an option to specify when) pww -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, 2009-04-09 at 11:41 +0100, Mark Shuttleworth wrote:
> Peter Whittaker wrote:
> > If you read my comments on the wiki page, you'll see I make clear
> > distinctions between system and user notifications: Let's apply that
> > distinction consistently. A user notification is a doorbell, it appears
> > in the user notification area, near where the user keeps their stuff. A
> > system notification is a firealarm and appears in the system
> > notification area, where other "systemy" things are.
> So, a user notification is something like "John emailed you", and a
> system notification is something like "Your network disappeared"?
Yes, exactly. They are different events, different types of events, and
need to be handled differently. If I ignore the doorbell, chances are
I've missed a friend or a chance to donate to a worthy cause; chances
are I'll have another chance at either/both.
If I ignore a firealarm, well, it's not the sort of thing you do more
than once, is it?
So "John emailed you" appears ephemerally in the user notification area
(mentally, I'm viewing this as bottom-right, where the bubble fades up
from the bottom, stopping with its bottom edge attached to the bottom
bar).
"Your network disappeared" appears in the system notification area,
using the same mechanism (my little mental picture is bubble fading down
from the top right, stopping with its bottom edge attached to the top
bar). If necessary, they can decorated with something akin to traffic
signals (yellow triangles for suspicious conditions, red octagons for
serious conditions, etc., though I would like this to be configurable).
Generally, user notifications are ephemeral, allowing us to ignore them;
the one obvious exception is a user-triggered reminder, that is, a
reminder of a ToDo, meeting, etc., entered by the user. (Preference
allows the user to make buddy or email notifications, etc., persistent
if they want, and all user notifications are user configurable.)
System notifications fall into three classes: The always ephemeral, the
always persistent, and the ephemeral-but-may-signal-a-problem. "Your
battery is about to die, save your work" is persistent (using the model
I described previously - appear, then sink beneath the focused window,
reappearing as focus rises). "Important updates are available" is also
persistent.
Always ephemeral would include "Your battery is fully charged", "you are
now connected to network N", etc.
Trickier are "ephemeral-but-may-signal-a-problem": "You are now
disconnected from the network" may or may not be a problem. Chances are,
you undocked your laptop. But if you aren't on a laptop, chances are
this is a problem.
I'm of at least two minds as to how to resolve this. My first - and
distinctly inelegant - inclination is to periodically remind the user
("You've been disconnected for 90 minutes, is everything OK"), perhaps
even making the notification persistent after a time, but this would be
disturbing to the laptop user who has deliberately gone off-line.
My second - and preferred - inclination is an ephemeral bubble to draw
attention coupled with a persistent NetworkManager icon showing current
network state. I say preferred because it is fairly easy to do (since it
is what happens now - no more work required) and because it is
relatively elegant. (The only reasonable improvement I can see is to not
raise the bubble until the machine is being used interactively, e.g.,
when the screen is unlocked, in order to ensure the bubble is displayed
when it makes sense to do so - when it can be attended to.)
My third - and downright potentially Rube Goldbergian - is to apply some
sort of heuristics to determine how likely it is that the network
disappearing was intended. If the machine is being used and it is a
latop, then chances are the user undocked; if the machine is not being
used, then maybe the user undocked, but that's not a safe assumption; if
the machine isn't a laptop, then chances are it's a problem - the user
may have deliberately unplugged the network, but that in itself likely
signals an unusual, so having to dismiss a persistent dialog won't be
too unwelcome.
And I don't know if the data exists to allow intelligent heuristics.
All of the ephemeral-but-may-signal-a-problem will have to be use-cased
(hmm, Calvin was right, verbing weirds language) to determine
appropriate defaults and appropriate heuristics.
What do we do if we get any of these wrong, as we surely will? We
discuss. We figure out default policies for all three cases, apply them
as best we can, likely succeeding more than we fail thanks to the 80/20
rule, and we debate the rest as a community and come to consensus.
Like we most often do.
Having said that, all system notif
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Thu, 2009-04-09 at 08:38 +0100, Mark Shuttleworth wrote: > Peter Whittaker wrote: > > The OS is different - when the computer needs > > to tell me something, I probably shouldn't ignore it. Think firealarm. > > > Yes, that's true. But there are some apps that have fire alarms too - > imagine, for example, an app which monitors your RAID array and > alerts you to failures and issues. Ah! Now you are thinking like a technologist and not a user, differentiating between the OS and applications based on whether they are kernel or user space, as opposed to what they actually do! >From the perspective of many - I would think most - users, something that monitors RAID - or monitors anything about the state of the computer for that matter - is not "an application", it's part of the computer. In that view, "applications" are things users start to get the computer to do what they want to do: email, IM, edit video, etc. > My point is that we should have clear guidelines about what > constitutes each mode of operation, and we should follow those as > rigorously with the OS as we would hope apps do, as well. If you read my comments on the wiki page, you'll see I make clear distinctions between system and user notifications: Let's apply that distinction consistently. A user notification is a doorbell, it appears in the user notification area, near where the user keeps their stuff. A system notification is a firealarm and appears in the system notification area, where other "systemy" things are. Both use the same underlying technologies - API calls that bring up bubbles - but the presentation is different: firealarms and doorbells are presented differently and both are different from normal apps. > As soon as we make exceptions for ourself we are weakening our > argument And foolish consistency makes a poorer system. Think back to the lack of PageUp/PageDown under OpenStep on the Next boxes, because Steve Jobs held the view it was a screen, not a page. So arrow keys giving you a line at a time were the only way to scroll. Jobs was being 100% consistent in his view, and missing the point that ScreenUp/ScreenDown would have been handy. > I *think* we're in agreement here :-) Actually, not so much. Hence all of the on-going debate on this. It's one thing to see a design, another to see the implementation. Some of us saw the design and said "cool". Many of us saw the implementation and said "Whoa, not cool". -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Wed, 2009-04-08 at 19:55 +, Mark Shuttleworth wrote: > I think it's important that we not treat the OS specially, Mark, thanks for your comments. I think this one area where there is considerable disagreement: The OS is different - when the computer needs to tell me something, I probably shouldn't ignore it. Think firealarm. But anything not from the OS - IM, email, etc. - is a doorbell that I can safely if I want. They are very different types and need to be presented differently so that users can easily recognize when which is a doorbell and which is a firealarm. Using the same signal presentation for both firealarms and doorbells is a bug - the same underlying technology can be used, but the signal presentation MUST be different. I covered this in more detail on the Comments page in the wiki. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
I've updated https://wiki.ubuntu.com/NotificationDesignGuidelines/Comment with my (very long) comments from this report and have added text to answer some of Matthew's questions and observations. The wiki post has a few differences from the bug report, mostly because my thinking got a little clearer: There are three zones (make the computer do something; what I'm actively doing; other things I'm doing or interested in) and two notification types (persistent system notifications appearing near the 'make the computer do something' zone, where the computer needs my help; ephemeral user notifications appearing near the 'other things' zone, where the computer tells about stuff I want to know about, like emails, IMs, etc.). The two notification types are firealarms and doorbells. Users can ignore or even disable doorbells, but firealarms are harder to ignore and only an admin can remove them. That's it in a nutshell, refer to the wiki page for details. -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Tue, 2009-04-07 at 16:25 +, Matthew Paul Thomas wrote: > I'm not sure from the text description how your proposed > persistent indicator would behave; perhaps you could post > a mockup and example timeline on the Ubuntu wiki? I'm not a graphics guy (I struggle with getting anything more than black-on-white bullets into presentations) so I'm not sure how to make a mock-up, but a timeline I can do. I assume that the right page would be https://wiki.ubuntu.com/NotificationDesignGuidelines/Comments ?? Or perhaps just what follows will do? 1. User has three windows open, FF, email, gedit. User is working in email. 2. Ephemeral notification appears - just like it works right now. A bubble appears, disappears after a few seconds, user can react or ignore. 3. Persistent notification appears: A bubble appears requesting user action, does not have focus, user continues working in email. After a few seconds, the bubble drops beneath the email window. 4. The user alt-tabs to FF - the persistent bubble moves to the top, above FF, but FF has focus. The user works within FF and the bubble drops beneath FF. The bubble appeared in the alt-tab list but the user didn't choose it. (This means that the window stack from desktop up is: gedit, email, the bubble, FF; FF has focus.) 5. The user minimizes FF - email now has focus but the bubble appears again. After a moment, it disappears. 6. The user clicks on show desktop - all windows are minimized, but the bubble is in the notification area, waiting for the user to click on it. As long as the desktop is displayed, the bubble is displayed. 7. The bubble never disappears. As long as the desktop is displayed, the bubble is displayed. If an application is open and has focus, the bubble pops above it briefly, then sinks beneath it again, taking top spot BUT NEVER FOCUS when focus changes to another application. 8. With the exception of "reboot needed", the persistent bubble is still there after reboot. 9. In the event of something urgent and important (Battery low, please save all work and plug in or shutdown), keep bringing the bubble up. When some threshold is reached, keep it on top, make it flash, make it ring a bell, but leave it there. Never take focus. 10. Pretty much nothing else is both urgent and important: If there is an email or an incoming phone call or anything else, display the bubble, then sink it away. If I choose to ignore it and continue working, that's my choice. Just like when I ignore the real phone while writing. 11. Never bring up a "real window" in the user zone. Ever. Only the user can do this. Everything else should be a bubble, either ephemeral or persistent, depending on urgency and importance. 12. The default policy should be that the only things that are important and urgent are those that involve potential data loss. Everything else is either urgent and unimportant - a phone call - or important and not urgent - an available update. 13. If I think one of the above not urgent and not important items is urgent and important, chances are I am sitting waiting for them and will respond to them when they arise. 14. If a user has a video open full screen, persistent and ephemeral will stay beneath the video. (It irks me when I am watching a video on full screen, hit the volume control on the keyboard, and the full screen disappears. Darned bubbles! :-> Other than that, I love the bubbles.) -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 332945] Re: [Jaunty] Update Notifier icon would provide useful status information
On Tue, 2009-04-07 at 14:21 +, Matthew Paul Thomas wrote: > It's not particularly productive to be covering, in bug report comments, > exactly the same points as were covered in the mailing list discussion > six weeks earlier. So if you could read the mailing list discussion > first, that would be awesome. :-) Thank you for your kind words. I did read the discussion - the entire interminable discussion :-> - and was left with the impression, perhaps mistaken, that the design approach that led to the original bug report was in fact still the intended approach. If this is incorrect - if the approach has changed in response to community feedback - then my apologies, I misread some of the later posts. If, on the other hand, the design approach remains the same despite counter-arguments both reasoned and inflamed, then I offer my $0.02 as to why this approach is terribly, terribly wrong. Hoping that the designers have heard the community, sincerely, pww -- [Jaunty] Update Notifier icon would provide useful status information https://bugs.launchpad.net/bugs/332945 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
