[Bug 383252] Re: Bad pixels other artifacts on fonts
I've been able to verify that Chromium does not use RENDER acceleration for antialiased fonts for web content; I asked one of the developers. That would seem to explain why it doesn't show up for Chromium web content (as stated in my previous comment). I believe this is a bug in EXA RENDER acceleration on the Radeon RV100. From https://blueprints.launchpad.net/ubuntu/+spec/radeon-change-xaa-to-exa : Extra efforts should be put into getting EXA issues forwarded upstream. ... I'm hoping my hunches/semi-educated guesses here fall under extra efforts. Cf: http://lists.freedesktop.org/archives/xorg/2006-July/016661.html -- this sounds like the same issue. Note that Despite the name (rv200), [the Radeon 7500 is] r100 based. (http://dri.freedesktop.org/wiki/ATIRadeon#head- 9161ac9470497d94f1a4f79794697347b20d5170). That report is from 2006. I could swear I was looking at a blog post on the commit of EXA RENDER accel support for Radeon the week before last, but I cannot find it now. I'll keep poking; it seems RV200 and RV100 and programmatically similar, and I'd like to ask if it was ever tested on RV100. -- Bad pixels other artifacts on fonts https://bugs.launchpad.net/bugs/383252 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 77649] Re: kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
This issue is no longer present in Karmic. I skipped Jaunty, so I can't speak for that release, but this is potentially closeable. -- kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set https://bugs.launchpad.net/bugs/77649 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 194029] Re: 2.6.24-8 Introduces Network Issue
This issue is gone in Karmic. I skipped Jaunty, so I cannot speak for that release, though I suspect it is fixed there too. This report is potentially closeable. -- 2.6.24-8 Introduces Network Issue https://bugs.launchpad.net/bugs/194029 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 72814] Re: Crash at login
Can anyone verify is this bug is still present? My G3-based Mac has died of old age. If not. yay! Please close this bug. If so, then it's time to officially drop support for the G3, whatever the value of Ubuntu PPC support may be. Maybe that's already been done; it so, I apologize. Please close this bug with the LP equivalent of invalid or something, then. -- Crash at login https://bugs.launchpad.net/bugs/72814 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 415897] Re: Thinkpad x40: palimpsest reports disk as failing when it isn't
*** This bug is a duplicate of bug 412152 *** https://bugs.launchpad.net/bugs/412152 ** This bug has been marked a duplicate of bug 412152 gnome-disk-utility nags me too much that my disk is failing -- Thinkpad x40: palimpsest reports disk as failing when it isn't https://bugs.launchpad.net/bugs/415897 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 416563] Re: Palimpsest disk utility found bad sector but the disk is healthy
*** This bug is a duplicate of bug 412152 *** https://bugs.launchpad.net/bugs/412152 ** This bug has been marked a duplicate of bug 412152 gnome-disk-utility nags me too much that my disk is failing -- Palimpsest disk utility found bad sector but the disk is healthy https://bugs.launchpad.net/bugs/416563 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 411750] Re: pango upgrade causes gnome-terminal to SIGSEGV
I've verified that the crash does not happen if gnome-terminal is not set to use a bitmap font. I've also reproduced the crash in GIMP: open the font selector for the text tool- crash. ** Visibility changed to: Public -- pango upgrade causes gnome-terminal to SIGSEGV https://bugs.launchpad.net/bugs/411750 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 383252] Re: Bad pixels other artifacts on fonts
I am also seeing this (on Karmic). Sometimes still readable is a stretch. It goes away if antialiasing is disabled. Bitmap fonts are unaffected. GTK and QT widgets are affected, as is the web content in a firefox window. The web content in chromium nightlies from http://ppa.launchpad.net/chromium-daily/ppa/ubuntu is not, despite being antialiased. Setting the AccelMethod for the ati driver to XAA seems to have made the problem go away. My card is Radeon RV100 QY [Radeon 7000/VE] which seems to be the same as the original reporter's. -- Bad pixels other artifacts on fonts https://bugs.launchpad.net/bugs/383252 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 400391] Re: totem crashed with SIGSEGV
I was able to get totem to play the NASA wmv stream after many crashes. So: it does work sometimes without gdb. It definitely appears to be timing-related. -- totem crashed with SIGSEGV https://bugs.launchpad.net/bugs/400391 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 400391] Re: totem crashed with SIGSEGV
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/29158205/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/29158206/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/29158207/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/29158208/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/29158209/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/29158210/Registers.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/29158211/ThreadStacktrace.txt ** Visibility changed to: Public -- totem crashed with SIGSEGV https://bugs.launchpad.net/bugs/400391 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 400391] Re: totem crashed with SIGSEGV
The failed retrace thing doesn't look like fun. I installed the libmms0-dbgsym, gstreamer0.10-plugins-bad-dbgsym libgstreamer0.10-0-dbgsym packages and got a backtrace from gdb, which I'm attaching. Totem frequently did not crash when run under gdb; I had to rerun it several times before the crash happened. If totem will sometimes run w/o crashing in the absence of gdb, I haven't seen it yet -- i.e. it crashes consistently. ** Attachment added: gdb-totem.txt http://launchpadlibrarian.net/29159589/gdb-totem.txt -- totem crashed with SIGSEGV https://bugs.launchpad.net/bugs/400391 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 250869] [NEW] synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 package from Debian unstable -- and
in the case of the latter, it does not exhibit the lags described in bug
#194029 -- yay!
A dump with Wireshark shows that the -4ubuntu1 client fails to complete
the synergy handshake with the server. I'll attach a .pcap file showing
the failed connection attempt. I've looked at the traffic from both
sides, and it's identical, i.e. the server sees what the client sends,
and vice versa. The last two packets in the dump are sent after sending
the client SIGQUIT (with Ctrl-\) and the two before it are from occur
after the connection times out. Before hitting Ctrl-\, netstat(8) on
the client shows the connection in CLOSE_WAIT.
The Ubuntu-specific changes to the upstream 1.3.1-4 package seem pretty
innocuous, so this is strange. I tried to rebuild the Debian source
package against intrepid, but the build failed due to Werror stuff -- I
need to hunker down and try to make it build, but it's not gonna happen
today. If anyone can provide any information on why the same source
builds on Debian, and not on Ubuntu, that would be useful.
I'll also attach the output of `synergyc -f -d DEBUG2 {server.name} and
an strace of the client when it fails to connect. The strace and
top(1)'s WCHAN field agree that the client is stuck in futex_wait.
So, lots of info; hopefully some of it's useful. What can I do to help
get this fixed?
Thanks.
** Affects: synergy (Ubuntu)
Importance: Undecided
Status: New
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
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 250869] Re: synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
** Attachment added: .pcap of failed connect of synergy client http://launchpadlibrarian.net/16237650/handshake_failed.pcap -- synergy-1.3.1-4ubuntu1 (intrepid) fails to connect https://bugs.launchpad.net/bugs/250869 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 250869] Re: synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
** Attachment added: Output of `synergyc -f -d DEBUG2 {server.name}`
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
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 250869] Re: synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
** Attachment added: strace of failed synergyc connect http://launchpadlibrarian.net/16237671/synergy_strace.txt -- synergy-1.3.1-4ubuntu1 (intrepid) fails to connect https://bugs.launchpad.net/bugs/250869 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 250869] Re: synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
Okay, it looks like the .pcap I attached doesn't include the last two packets I described in the original report -- i.e. the last two packets are from the connection timing out, and the two packets I once saw after Ctrl-\'ing the client aren't in there. Maybe they weren't sent this time (though I saw them before) and maybe it's PEBKAC on my part. The last two packets *not* here, IIRC, are a packet from the client with FIN set, and a response from the server that has ACK or RST set, depending on how long it had been since the server tried to close the connection. Sorry about that. -- synergy-1.3.1-4ubuntu1 (intrepid) fails to connect https://bugs.launchpad.net/bugs/250869 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 250869] Re: synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
...and I should have said hardy, not gutsy, in all instances above. I'm walking away from the keyboard now. ;-) -- synergy-1.3.1-4ubuntu1 (intrepid) fails to connect https://bugs.launchpad.net/bugs/250869 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 194029] Re: 2.6.24-8 Introduces Network Issue
This bug has been triaged; the cause of the bug seems to be known. Yes, the root cause of this bug can introduce lags and general desktop unresponsiveness in other applications. It's a kernel scheduler option that's known to the (upstream) developers to cause scheduling problems and which has unfortunately been enabled in the Hardy 8.04 release. The fix seems to be in the pipeline: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=273f7b551a420580307fa414fe616f0e276a4035 Hopefully this will be released as an update soon. (not affiliated with Ubuntu or Canonical in any way, myself) -- 2.6.24-8 Introduces Network Issue https://bugs.launchpad.net/bugs/194029 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 196792] Re: Ubuntu 8.04 synergy lagging
I am seeing this as well. It's a fair bet this is https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/91540 turning up again. -- Ubuntu 8.04 synergy lagging https://bugs.launchpad.net/bugs/196792 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 77649] Re: kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
This still doesn't work in Gutsy: | The UTS Release version in include/linux/utsrelease.h | 2.6.23-ge8b8c977-dirty | does not match current version: | 2.6.23-ge8b8c977-dirty-ge8b8c977-dirty-dirty | Please correct this. | make: *** [install/linux-image-2.6.23-ge8b8c977-dirty-ge8b8c977-dirty- dirty] Error 2 ...which seems to be related to the problem described in Debian bug #446879. That report doesn't mention it causing make-kpkg to fail, though. -- kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set https://bugs.launchpad.net/bugs/77649 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149729] [Gutsy] dpkg thinks /usr/share/cups/model/gutenprint should exist
Public bug reported: Binary package hint: cupsys-driver-gutenprint The output of `dpkg -L cupsys-driver-gutenprint` indicated that dpkg thinks /usr/share/cups/model/gutenprint should exist, but it is not present even after purging the package (needed --force-depends) and reinstalling it. The symlink is present in the package - it's there when the deb is extracted with `dpkg-deb -x`. Maybe the symlink is not being created because its target (/usr/share/ppds/gutenprint) does not exist? I don't know if this will cause an actual problem, but it doesn't seem right that dpkg thinks it's installed a file, but hasn't. ** Affects: gutenprint (Ubuntu) Importance: Undecided Status: New -- [Gutsy] dpkg thinks /usr/share/cups/model/gutenprint should exist https://bugs.launchpad.net/bugs/149729 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 72814] Re: Crash at login
I can confirm that backing out the above patch and rebuilding the package makes GNOME work again on my PowerPC G3. Please re-open this bug. The open bit of this bug refers to the need to figure out why Altivec detection is broken, so that it can be re-enabled without breaking G3s. Ubuntu's problem is that Altivec detection has somehow been re-enabled, and is still broken. It doesn't appear to me that Debian has this problem. (just trying to be clear) -- Crash at login https://bugs.launchpad.net/bugs/72814 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 87382] Re: rpc.idmapd not working
I'm seeing this too, with 1.0.11~git-20060105-2 (i.e. feisty). I strace'd mount(8), and see that mount prints that warning just after failing to locate the file /var/run/rpc.idmapd.pid. The warning seems to be spurious -- rpc.idmapd is running, and I'm seeing the correct owners on the mounted NFSv4 share. Gustavo, do the files on your own NFS mount have the correct owners? Adding the --pidfile parameter to start-stop-daemon does make the error go away here, but it's necessary to pass --make-pidfile also. This used to work, though -- mount only printed the message when rpc.idmapd was in fact not running. I'm attaching a diff that demonstrates the change I made to /etc/init.d /nfs-common . ** Attachment added: Ask start-stop-daemon to make a pidfile http://librarian.launchpad.net/7034306/nfs-common.diff -- rpc.idmapd not working https://launchpad.net/bugs/87382 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86870] Re: /usr/lib/dri/i915_dri.so missing (feisty)
This is i386. I had version 6.5.1~20060817-0ubuntu4 -- this got updated to 6.5.2-3ubuntu1 today and the the file is there as you say. I'm not seeing any problems with this anymore either. Thank you. -- /usr/lib/dri/i915_dri.so missing (feisty) https://launchpad.net/bugs/86870 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86870] /usr/lib/dri/i915_dri.so missing (feisty)
Public bug reported: # export LIBGL_DEBUG=verbose # glxinfo name of display: :0.0 libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0) libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so: cannot open shared object file: No such file or directory) libGL error: unable to load driver: i915_dri.so display: :0 screen: 0 direct rendering: No # dpkg -L libgl1-mesa-dri /. /usr /usr/lib /usr/lib/dri /usr/lib/dri/ffb_dri.so # lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03) This is feisty, up to date for today, with both the ubuntu-desktop and kubuntu-desktop packages installed. The xorg.conf was automatically generated, and AIGLX is enabled. The xorg.log.0 says direct rendering is enabled. glxgears draws very slowly, and flickers badly enough that the 3D image is distorted. Moving or resizing the window crashes the X server (which would be a different bug). I've seen this behavior for (at least) a month now. So -- is this a bug, or some AIGLX thing -- i.e. should I expect that file to exist, or do I need to report the other bug to upstream (I can do that -- I'm guessing the relevant people would be the DRI/DRM maintainers? So I should report it against the latest mainline kernel?) Thanks for any help in narrowing down the source of this problem. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Unconfirmed -- /usr/lib/dri/i915_dri.so missing (feisty) https://launchpad.net/bugs/86870 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54621] Re: Kernel panic - not syncing: IO-APIC + timer doesn't work!
Any movement on this? It'd be nice to submit a fix for this to the mainline kernel within the three week window after 2.6.20 is released (RSN). -- Kernel panic - not syncing: IO-APIC + timer doesn't work! https://launchpad.net/bugs/54621 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42049] Re: no direct rendering on dapper with i810 chipset (855GM)
Do you get any error messages if you export LIBGL_DEBUG=verbose before running glxinfo? They'd show up in the terminal window, not the logs. -- no direct rendering on dapper with i810 chipset (855GM) https://launchpad.net/bugs/42049 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
@Mr. Daley: Luke, you are proposing to add a special case to the Services dialog for avahi You are proposing to special-case the avahi-daemon initscript. I won't speculate as to why. I have demonstrated that this behavior is very common in Debian, and so in Ubuntu, and I don't see that you have responded to that in any way. This is a long-established way for initscripts in Debian to behave. Making Avahi behave differently because -- well, I don't know -- would be inconsistent, and you have not provided a justification for it that I can see. Rewriting every initscript for Ubuntu to remove this Debian feature is not likely to happen, I think -- especially not for packages in universe. If you're argument is against disabling a daemon's initscript in /etc/default alone, please propose that this behavior be removed from Debian on the debian-devel mailing list, and let us know who that turns out. Linking to the Upstart manifesto seems disengenious to me. I cannot claim to speak for the authors of that document, but I can't imagine they meant that this established behavior be removed from Debian and it's derivatives. -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
Bah, there are many precedents in Debian and Ubuntu for this behavior. Making /etc/init.d/avahi-daemon ignore the system setting in /etc/default because people are too lazy or stupid to read the initscript is dumb when many other packages work this way, including many in universe (that won't be similarly changed). What happens when you edit /boot/grub/menu.lst, and don't respect the Debian/Ubuntu way of doing things? It gets clobbered the next time update-grub is run. What happens when you add a line to /etc/modprobe.conf? You get to keep both pieces. Ubuntu isn't Gentoo, or SysV. That upgrading to edgy from dapper silently turned off avahi-daemon is a bug, IMHO, but making /etc/init.d/avahi-daemon ignore /etc/default is not a fix for that. What happens when people helpfully add the missing SysV runlevel symlink for avahi-daemon, and things stop working correctly? The best answer is you get to keep both pieces, but only after hard-to- understand bug reports. Or perhaps it's more well don't do that then which equally applies to this. If something really must be done for this bug, move the avahi- daemon script out of /etc/init.d, so people don't find it and expect it to work a certain way. -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56426] Re: /etc/init.d/avahi-daemon is useless
Ubuntu is supposed to be for everyone and many people wouldn't be able to figure this out. If you can't figure this out, you oughtn't be fiddling around with the SysV init scripts. They're not for everyone. Things should just work, without needing to mess with the initscripts. Once you do, you accept the responsibility to figure it out. There's a toggle in GNOME: System-Administration-Networking-General-Automatic service discovery It makes the change in /etc/default/avahi-daemon. When someone decides to turn on avahi-daemon with a SysV symlink, that toggle will stop working. (The many packages whose daemons can be disabled via debconf (which usually does the same thing) will have the same problem.) If there's no way to turn that avahi thing on in $DESKTOP that's a bug. That avahi silently stopped working on upgrade, is a bug (that pref is hard to find!). This is NOTABUG. As for precedents, a quick poke around in my /etc/init.d turns up no other examples of conditional startup installed at the moment. You almost certainly do. You would have had better luck looking in /etc/default: apache2 apt-cacher avahi-dnsconfd bittorrent bootlogd (initscripts package) dbus (and dbus-1) ddclient fetchmail hal hplip mdadm mldonkey-server nfs-common (toggles for a number of daemons with a single initscript) portmap prelink rscsi (refuses to run if the file in /etc/defaults is missing) rsync samba smartmontools spamassassin watchdog All of those packages (on my system) have the same sort of toggle in /etc/defaults (that affects the init.d script) -- many of them have a file in /etc/defaults for only that purpose. This is a Debian standard, just like the alternatives system, update- grub, update-mime, and all their friends. -- /etc/init.d/avahi-daemon is useless https://launchpad.net/bugs/56426 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50273] Re: Panel crashes on the 'run application' dialog when assistive technologies are enabled
I'm seeing this too -- running anything from the Run dialog causes gnome-panel to crash. Turning assistive technologies off makes the problem go away. -- Panel crashes on the 'run application' dialog when assistive technologies are enabled https://launchpad.net/bugs/50273 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 51639] can't use vesafb with lilo
Public bug reported: When using the lilo.conf vga= parameter, 'vga=' doesn't turn up in the kernel command line. Further, lilo won't allow putting 'vga=' into the kernel command line directly via 'append' or 'literal'. This means that it's not possible to use vesafb with with lilo -- the usplash scripts won't see 'vga=' and so won't load vesafb. ** Affects: usplash (Ubuntu) Importance: Untriaged Status: Unconfirmed -- can't use vesafb with lilo https://launchpad.net/bugs/51639 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
