[Bug 1531184] Re: dnsmasq doesn't start on boot because its interface isn't up yet
I have openvswitch-switch, which did required from me to apply some changes to systemd service file that seems not to be aware of virtual devices up. So, bottom line, /etc/network/interface files are taking action in a way that smashes the rush to boot up, so dnsmasq also become a victim, and for me the solution above was not compatible. So I had to add to dnsmasq.service the follow lines: Requires=sys-subsystem-net-devices-.device After=sys-subsystem-net-devices-.device Wants=sys-subsystem-net-devices-.device Got the above info from systemctl --full | grep subsystem Best regards! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: dnsmasq doesn't start on boot because its interface isn't up yet To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351286] Re: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE
I have a fresh install for Ubuntu 16.04, updated, and same issue. After read the peterK (peter-kanderholm) post wrote on 2016-01-08, I couldn't accept it, I do use regular basis a scanner... Then per the bug reported I did remember the "Color" and "Color Profile Viewer", entered there and almost immediately was recommended to install Gnome Color Manager, accepted. Then twice reboot no bug, no more crashes. I do remember this come after I did plug a second monitor to my laptop, could this be a coincidence? Regards! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351286 Title: colord-sane assert failure: colord-sane: simple-watch.c:454: avahi_simple_poll_prepare: Assertion `s->state == STATE_INIT || s->state == STATE_DISPATCHED || s->state == STATE_FAILURE' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1351286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
Hi! First, thanks! Second, the answer is that the issue is different since December, I think. So I do not use the alsa force-reload, which is commented out since. I'm now able to get sound but erratically the sound is muted, full or some other level, which doesn't have nothing to do what I leaved last shutdown. I have 10.04 installed and following hardly the updates using VMWare strategically configured using physicall partitions, so some times I boot live the installation. I going to do some boots on my 10.04 and tell you. Bye! Tomas On 27-03-2010 23:37, Brad Figg wrote: Hi Sarraceno, Please, if you are still having issues, test with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you run the following command from a Terminal (Applications-Accessories-Terminal). It will automatically gather and attach updated debug information to this report. apport-collect -p alsa-base 467619 Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] ** Tags added: kj-triage needs-required-logs needs-test-current-image no-sound-system ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
Hi! So, te tests were: Pre reboot I did changed settigns and also not changing settings. Then reboot Whe machine come up 10.04 chown no issue with sound, setting prevailed and I had real sound. Thanks! Good job! Tomas On 27-03-2010 23:37, Brad Figg wrote: Hi Sarraceno, Please, if you are still having issues, test with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If it remains an issue, could you run the following command from a Terminal (Applications-Accessories-Terminal). It will automatically gather and attach updated debug information to this report. apport-collect -p alsa-base 467619 Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results. [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.] ** Tags added: kj-triage needs-required-logs needs-test-current-image no-sound-system ** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
After a couple of days installing everything fresh taking out any trick. I do not know what is the relation, after adding a second user to the laptop, after reboot sound didn't work. alsa force-reload made to worked again. Does anyone know about any module setting related to this sympthoms? ** Changed in: gst0.10-python (Ubuntu) Status: Invalid = New -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
I think you are referring module linux-backports-modules-alsa-karmic- generic, not installed, after reboot I'll come here to say if worked. -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
No, still not ok. After post this bug I did upgrade two of my computers from 9.04 into 9.10n (Ubunut Desktop, Ubuntu Studio) at home, only mediacenter is waiting, I need to be sure that one having sound after upgrade. So, on the two I upgraded are fine, for for those I answered always to replace config files, for my work laptop I didn't begin afraid of next day I would have the machine available to go work... So, it's possible that I need to refresh/reconfigure some package. Does any one know what? The packages for alsa that I have are: jto...@ptjtomasub:~$ apt-show-versions -r '.*alsa.*' alsa-base/karmic uptodate 1.0.20+dfsg-1ubuntu5 alsa-utils/karmic uptodate 1.0.20-2ubuntu6 bluez-alsa/karmic uptodate 4.51-0ubuntu2 gnome-alsamixer/karmic uptodate 0.9.7~cvs.20060916.ds.1-2 gstreamer0.10-alsa/karmic uptodate 0.10.25-2ubuntu1 libesd-alsa0/karmic uptodate 0.2.41-5 libsdl1.2debian-alsa not installed libsox-fmt-alsa/karmic uptodate 14.3.0-1build1 linux-backports-modules-alsa-2.6.31-14-generic/karmic uptodate 2.6.31-14.16 linux-backports-modules-alsa-karmic-generic/karmic uptodate 2.6.31.14.27 jto...@ptjtomasub:~$ I have did dpkg-reconfigure for all these except the backports that were no installed, result is none. -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] [NEW] After upgrade, no sound. If I manually run alsa force-reload sound becomes available
Public bug reported: I'm just doing a clean report since last report. I did some investigation and discovered that alsa force-reload is an work around... ProblemType: Bug Architecture: i386 CheckboxCommand: gst_pipeline_test -t 2 'audiotestsrc wave=sine freq=512 ! audioconvert ! audioresample ! gconfaudiosink' CheckboxDescription: Click the Test button to play a sound on the automatically detected playback device. Do you hear a sound? CheckboxSubmission: ba33e8f38e4f0f41eacc0d477c7bafe8 CheckboxSystem: 2710f0ed8779c17355929d29bbe825af CheckboxTest: playback_auto Date: Sat Oct 31 23:04:44 2009 DistroRelease: Ubuntu 9.10 Package: python-gst0.10 0.10.17-1 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: gst0.10-python Tags: checkbox-bug Uname: Linux 2.6.31-14-generic i686 ** Affects: gst0.10-python (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug checkbox-bug i386 -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
** Attachment added: CheckboxData.txt http://launchpadlibrarian.net/34818527/CheckboxData.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/34818528/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/34818529/XsessionErrors.txt -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 458737] Re: No Sound or outputs M-Audio Delta 44 ICE1712
guys! Try sudo alsa force-reload, for me did worked... and comment you results, pls. -- No Sound or outputs M-Audio Delta 44 ICE1712 https://bugs.launchpad.net/bugs/458737 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 467619] Re: After upgrade, no sound. If I manually run alsa force-reload sound becomes available
I forgot to say that: for my users I did check permissions for audio using the Users and Groups manager. So I don't understant why sudo alsa force-reload gets the following output: -- jto...@ptjtomasub:~$ sudo alsa force-reload [sudo] password for jtomas: lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs Output information may be incomplete. Terminating processes: 1358 3068lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs Output information may be incomplete. 3268lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs Output information may be incomplete. . lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/jtomas/.gvfs Output information may be incomplete. Unloading ALSA sound driver modules: snd-hda-codec-si3054 snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm-oss snd-mixer-oss snd-pcm snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc (failed: modules still loaded: snd-hda-codec-si3054 snd-hda-codec-realtek snd-hda-codec snd-hwdep snd-pcm snd-timer snd-page-alloc). Loading ALSA sound driver modules: snd-hda-codec-si3054 snd-hda-codec-realtek snd-hda-intel snd-hda-codec snd-hwdep snd-pcm-oss snd-mixer-oss snd-pcm snd-seq-dummy snd-seq-oss snd-seq-midi snd-rawmidi snd-seq-midi-event snd-seq snd-timer snd-seq-device snd-page-alloc. jto...@ptjtomasub:~$ -- -- After upgrade, no sound. If I manually run alsa force-reload sound becomes available https://bugs.launchpad.net/bugs/467619 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 357582] Re: [Acer, inc. TravelMate 8210] suspend/resume failure
Hi! Answer back to you... Wit karmic koala seems hibernate or supend wosks fine. about 10 times hibernation no issue. First I did notice lack off sound, but that is another issue. Thanks! -- [Acer, inc. TravelMate 8210] suspend/resume failure https://bugs.launchpad.net/bugs/357582 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 358075] Re: [Acer, inc. TravelMate 8200] suspend/resume failure
handled by Bug #357582. close this one! Thanks -- [Acer, inc. TravelMate 8200] suspend/resume failure https://bugs.launchpad.net/bugs/358075 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 357582] Re: [Acer, inc. TravelMate 8210] suspend/resume failure
Yup! Late, but just for one reason, you were answering me and my laptop power supply unit was going burned some how... I have not using hibernation or suspend, but soon I get a new power supply unit I'll take your request. Thanks! On Tue, Aug 18, 2009 at 5:51 PM, Leann Ogasawara leann.ogasaw...@canonical.com wrote: Hi Vilhow, This was reported a while ago but hasn't had any recent activity. Can you confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release. ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . You should be able to test Suspend from a LiveCD. If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Finally, if you could also take a look at https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume and provide answers to the questions mentioned under the Information Gathering section that would be great. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- [Acer, inc. TravelMate 8210] suspend/resume failure https://bugs.launchpad.net/bugs/357582 You received this bug notification because you are a direct subscriber of the bug. Status in “linux” package in Ubuntu: Incomplete Bug description: The fan turned off just like it does in Vista. It hanged when I powered the computer on again. Fan was on again but nothing happened. I had to use 'force' (press the power button for 5 secs) to power it off. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: Acer, inc. TravelMate 8210 Package: linux-image-2.6.28-11-generic 2.6.28-11.40 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=ccee43d1-1f24-4eae-b7dd-0c056ead90da ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.40-generic SourcePackage: linux Tags: resume suspend Title: [Acer, inc. TravelMate 8210] suspend/resume failure UserGroups: -- José Fortunato Tomás @ GMail Φ Skype: jfhtomas Φ MSN: j...@netc.pt Φ ICQ: 25099687 -- [Acer, inc. TravelMate 8210] suspend/resume failure https://bugs.launchpad.net/bugs/357582 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 357582] Re: [Acer, inc. TravelMate 8210] suspend/resume failure
Hi! I do not want to use Vista regarding the storage requirements and so on... or XP or Ubuntu, never Vista... :-) I had to get out, so hit suspend. 4h after I hit power up. machine had an response as come back, but only fan, hdd, leds. Screen didn't get any light. Thanks! -- [Acer, inc. TravelMate 8210] suspend/resume failure https://bugs.launchpad.net/bugs/357582 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 358075] [NEW] [Acer, inc. TravelMate 8200] suspend/resume failure
Public bug reported: I was following https://wiki.ubuntu.com/KernelTeam/SuspendResumeTesting instructions and during step STEP 4 the machine didn't come up correctly. More specifically: machine start to come up puting every ligth on and any spining object spining (fan, HDD), screen black but with some back ligth. Some HDD access seamed to be happening at the beginning, but nothing happened then this. 4 seconds power button needed to restart machine. ProblemType: KernelOops Annotation: This occured during a previous suspend and prevented it from resuming properly. Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InterpreterPath: /usr/bin/python2.6 MachineType: Acer, inc. TravelMate 8200 Package: linux-image-2.6.28-11-generic 2.6.28-11.41 ProcAttrCurrent: unconfined ProcCmdLine: root=UUID=c84717e4-dd04-4c28-a94c-46c52f8d0dbf ro quiet splash ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume ProcEnviron: PATH=(custom, no user) ProcVersionSignature: Ubuntu 2.6.28-11.41-generic SourcePackage: linux Tags: resume suspend Title: [Acer, inc. TravelMate 8200] suspend/resume failure UserGroups: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-kerneloops i386 resume suspend -- [Acer, inc. TravelMate 8200] suspend/resume failure https://bugs.launchpad.net/bugs/358075 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 358075] Re: [Acer, inc. TravelMate 8200] suspend/resume failure
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/25082126/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/25082127/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/25082128/Dependencies.txt ** Attachment added: HalComputerInfo.txt http://launchpadlibrarian.net/25082130/HalComputerInfo.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/25082131/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/25082132/Lsusb.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/25082133/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/25082134/ProcInterrupts.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/25082135/ProcMaps.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/25082136/ProcModules.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/25082137/ProcStatus.txt ** Attachment added: SleepLog.txt http://launchpadlibrarian.net/25082139/SleepLog.txt ** Attachment added: StressLog.txt http://launchpadlibrarian.net/25082140/StressLog.txt -- [Acer, inc. TravelMate 8200] suspend/resume failure https://bugs.launchpad.net/bugs/358075 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
