** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939114
Title:
vino-server crashed with SIGSEGV
To manage notifications about this bug go to:
This might be a duplicate of #879496.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939114
Title:
vino-server crashed with SIGSEGV
To manage notifications about this bug go to:
It took a while to get back to this, but here are yaboot.conf and the
boot message:
yaboot.conf:
##
boot=/dev/sda2
device=/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED]/@12:
partition=3
root=/dev/sda3
timeout=50
install=/usr/lib/yaboot/ofboot
enablecdboot
I still see it in both Edgy and Feisty. The boot process seems to find
yaboot on /dev/sda2, but cannot find stage 1, hangs for a while, and
loops back to stage 1. I'll post yaboot.conf and stage 1 boot message
later today.
--
dapper kernel doesn't boot from scsi disk on b/w G3 (powerpc)
The failure is still present when the remote server is a PPC platform. From
both Edgy and Feisty clients (vncviewer) on
i386 platforms, and vino-server on the PPC platform with a password specified,
the response is
VNC authentication failed'. Without a password specified, the response is
as
A little more information. This was working just fine when the original
PPC installation was Herd-4 with dist-upgrades on an almost daily basis.
The problem appeared when I did a fresh install of the Feisty PPC
release (ports, alternate install iso).
--
vncviewer does not work if a password is
I see this, too.
System: Dell Inspiron 2650
Wifi card: Zonet 1701 (Ralink 2560)
DistroRelease: Ubuntu 7.04
Uname: Linux playroom 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007
i686 GNU/Linux
Date: Sun 31 Mar 1007 17:50 (PDT)
I use a static IP address behind a Linksys WRT54G.
Correction.
The command sudo ifup ra0 produces a message that says
something like device ra0 already configured, and the card
is remains off. I have to run sudo ifdown ra0 first in order
for the card to be initialized successfully by ifup.
My current workaround is to put the line
The problem has not appeared again until recently, after a dist-upgrade shortly
after the herd5 release, and persisted after a dist-upgrade today (18mar07
PDT). At that time both Mixer and Trash applets did not start at login. I
examined the
gnome-applets version as a matter of course and
(that's PST, not PDT)
--
[apport] powerpc - mixer_applet2 crashed with SIGILL during Desktop init
https://launchpad.net/bugs/83100
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The mixer-applet2 crash notification stopped over a week ago after a
dist-upgrade. The Gnome Settings Daemon notification still appears
today after a dist-upgrade about 20 minutes ago (it's now 10:50 AM PDT,
18:50 UTC).
The Gnome Settings Daemon startup error is also reported in Bug #84876
(and
Public bug reported:
Binary package hint: gnome-applets
Install herd3 on iMac G3/350 using the powerpc alternate cd.
The crash happens at the very first login. A notification window
appears during Desktop initialization that says:
There was an error starting th Gnome Settings Daemon.
...
** Attachment added: CoreDump.gz
http://librarian.launchpad.net/6172772/CoreDump.gz
** Attachment added: Dependencies.txt
http://librarian.launchpad.net/6172773/Dependencies.txt
** Attachment added: ProcMaps.txt
http://librarian.launchpad.net/6172774/ProcMaps.txt
** Attachment added:
A workaround is suggested by user radwis in thread
http://ubuntuforums.org/showthread.php?t=276642
Add the boot option acpi=force to the kernel line
in /boot/grub/menu.lst. It works for me. Here's
my Edgy boot clause:
title Kubuntu Edgy 6.10, kernel 2.6.17-10-generic
root
This happens in my Kubuntu Edgy, too (Dell 2650), and
didn't start happening unitl I updated about 3 hours ago.
There are two threads at the Ubuntu Forums (Edgy)
reporting this:
http://ubuntuforums.org/showthread.php?t=273400
http://ubuntuforums.org/showthread.php?t=276642
--
[edgy]Shutdown
Note that section ServerLayout aslo contains references
to these devices:
Section ServerLayout
Identifier Default Layout
Screen Default Screen 0 0
InputDeviceGeneric Keyboard
InputDeviceConfigured Mouse
InputDevicestylus SendCoreEvents
InputDevice
I think it's for tablet users to have out of the box tablet support.
But that's without warranty ;-)
Why would tablet users get special consideration?
xorg configuration missed my Synaptics touchpad in
Edgy, but not in Dapper. I want special consideration,
too.
--
wacom entries appear even
17 matches
Mail list logo
