To start as an affiliate marketer, you must have a site on which to place
links to the products or services you recommend. There are many inexpensive
website services such as Hostgator and GoDaddy. It's also easy to set up a
free blog through services such as Google's Blogger blog
Thanks! This worked also for me (still on KDE 4.4)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/553567
Title:
transition from plymouth to kdm not smooth
To manage
Required mainline driver functionality is now included in linux-next and should
be part of linux 2.6.38.
See
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=blob;f=drivers/net/wireless/rt2x00/Kconfig;h=6f383cd684b009a1cee9663768759c32772a7cf1;hb=HEAD
** Changed in: linux
** Changed in: ubiquity (Ubuntu)
Status: Incomplete = New
--
slideshow windowed and with wrong message in ubiquity-only mode
https://bugs.launchpad.net/bugs/542626
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Still present on Maverick and kde 4.5 (intel gpu).
--
transition from plymouth to kdm not smooth
https://bugs.launchpad.net/bugs/553567
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in ubuntu.
--
kubuntu-bugs mailing list
The problem is reduced but still present in Maverick: the slideshow is
now properly displayed, but the misleading message about exploring the
live session is still there (at least in the italian locale)
--
slideshow windowed and with wrong message in ubiquity-only mode
Please note that simply making an upstart config file starting on
started networking will NOT work, as that signal is emitted before
bridges are brought up. The problem may be solved by integrating upstart
conversion with Ian McMichael solution, and making dhcp3 start when net-
device-up has been
Adding random sleeps is usually not the best possible solution, as the
required delay varies between systems (for example, when using a network
bridge). Maybe depending on net-device-up would be better.
--
sshd will not start at boot if ListenAddress is set, because network interface
is not yet
Please note that simply making an upstart config file starting on
started networking will NOT work, as that signal is emitted before
bridges are brought up. The problem may be solved by integrating upstart
conversion with Ian McMichael solution, and making dhcp3 start when net-
device-up has been
Adding random sleeps is usually not the best possible solution, as the
required delay varies between systems (for example, when using a network
bridge). Maybe depending on net-device-up would be better.
--
sshd will not start at boot if ListenAddress is set, because network interface
is not yet
Thanks dmb. You were faster than my complain :-))
Any progress in mainline integration?
Tkanks again
--
HVR-1300 HVR-3000 HVR-4000 broken in kernel
https://bugs.launchpad.net/bugs/439163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using nouveau from xorg-edgers and 2.6.34 kernel fixed the issue for me,
even with no blacklisting. It would be quite problematic for me to
downgrade, but I think it will be easier to backport a patch rather than
writing a new one.
--
[lucid] nouveau driver fails to switch virtual terminal
It seems that kdm ignores X option nr if autologin is enabled. I
looked at both kdm source and plymouth transition patch but it's quite
complex there.
--
transition from plymouth to kdm not smooth
https://bugs.launchpad.net/bugs/553567
You received this bug notification because you are a member
Marco's procedure is actually incomplete. You shoud also add set
gfxpayload=keep in /etc/grub.d/00_header under set
gfxmode=${GRUB_GFXMODE} and run update-grub. You may also have to
unblacklist vesafb and rebuild your initramfs.
--
plymouth theme ugly on binary nvidia driver
I've exactly the same issue. Currently I have a single monitor, but two
video cards (285 GTX).
--
[lucid] nouveau driver fails to switch virtual terminal
https://bugs.launchpad.net/bugs/546678
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: ubiquity
When run in ubiquity-only mode, the slideshow is displayed in a window
on a black background (after a fullscreen setup program) and asks the
user to try the features of (k)ubuntu while installing, which is
obviously impossible. This may be
This happens because there are different revisions of this adapter. The
latest one, B2 (id 07d1:3c0a), uses the 3070 chipset and the rt2800usb
driver doesn't work with it. My solution was to build a 2.6.33 kernel
with rt2800usb disabled and rt3070 FROM STAGING enabled. Hopefully that
driver will
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
Wireless DLINK Adapter DWA-140 not working
https://bugs.launchpad.net/bugs/507375
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Same here (cups, kvm). I'm rather surprised this bug isn't marked as
critical: we're talking about a large part of operating system services,
and this may also produce security issues (firewall not starting etc).
At least they could revert to version 0.6.3-10 as a temporary fix.
--
upstart not
Still getting this error on karmic server 64-bit. This seems a killer
bug as it prevents netinstalling from a local mirror (except using apt-
mirror).
--
missing main/debian-installer in repo causes debmirror to fail
https://bugs.launchpad.net/bugs/34376
You received this bug notification
Sorry, when I wrote fixed with kvm-85 I was using kernel 2.6.29.1 from
mainline ppa. I didn't have to change anything in xorg.conf, though.
--
[jaunty] vesa driver stopped working (no devices found) inside KVM after X
update
https://bugs.launchpad.net/bugs/356133
You received this bug
Sorry, when I wrote fixed with kvm-85 I was using kernel 2.6.29.1 from
mainline ppa. I didn't have to change anything in xorg.conf, though.
--
[jaunty] vesa driver stopped working (no devices found) inside KVM after X
update
https://bugs.launchpad.net/bugs/356133
You received this bug
This bug is fixed with kvm-85 and 20090420 image, but I think it's too
late to include it in jaunty.
--
[jaunty] vesa driver stopped working (no devices found) inside KVM after X
update
https://bugs.launchpad.net/bugs/356133
You received this bug notification because you are a member of Ubuntu
Well, the best guess I can do is that the Ubuntu xorg upgrade made xorg
itself more strict when dealing with vesa cards. Maybe te KVM emulated
card wasn't completely compliant with the standards. Please note that
this is a complete guess, and may be completely incorrect. Can you
confirm kvm-85
I tried running apt-get -b source xserver-xorg-video-vesa (to get a
module compiled for the right xorg version) but the problem remains the
same.
--
[jaunty] vesa driver stopped working (no devices found) inside KVM after X
update
https://bugs.launchpad.net/bugs/356133
You received this bug
Confirmed on amd64.
The vesa module seems still from a prerelease of xorg (version 1.5.99).
** Changed in: xserver-xorg-video-vesa (Ubuntu)
Status: New = Confirmed
--
[jaunty] vesa driver stopped working (no devices found) inside KVM after X
update
https://bugs.launchpad.net/bugs/356133
Patch written
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = KBios (kbios)
--
x not starting in kvm with std vga
https://bugs.launchpad.net/bugs/338219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
After diving deeply into X manainer scripts and other stuff, I found the
problem. The livecd uses /usr/bin/dexconf to generate xorg.conf. If you
look at line 191, you'll see
QEMU_KVM=$(grep QEMU Virtual CPU /proc/cpuinfo || true)
if [ -n $QEMU_KVM ]; then
DEVICE_DRIVER=cirrus
fi
So the
Ok, here's my patch. It is as simple as possible, and may not be the
best possible solution.
** Attachment added: dexconf patch
http://launchpadlibrarian.net/24412615/dexconf.patch
--
x not starting in kvm with std vga
https://bugs.launchpad.net/bugs/338219
You received this bug notification
Today I tried qemu 0.10.1 (which has kvm support), as the changelog
reported kvm vga: fix screen corruption with Ubuntu installations
(Glauber Costa). However, it has exactly the same problems as kvm
userspace. I tried running lspci and the result is the same as in my
previous post.
--
x not
Ups, sorry for that.
Here is the result of lspci -vvnn.
Also, when kvm is started this way, usplash doesn't work. May it be related to
this bug?
Thanks
** Attachment added: lspci
http://launchpadlibrarian.net/23997398/lspci
--
x not starting in kvm with std vga
I think the simplest solution would be to make the bare gtk library
depend on libbonoboui: that way, every gtk app would work without
packaging changes.
** Changed in: gtk-qt-engine (Ubuntu)
Status: New = Confirmed
--
[Kubuntu 9.04] gtk-qt-engine not working
The latest SVN revision (61) adds support for KDE 4.2. I tested it and it works
very well.
Is it possible to include it in Jaunty?
** Changed in: ubuntu
Status: Invalid = New
--
[needs-packaging] Email Notify Plasmoid
https://bugs.launchpad.net/bugs/229537
You received this bug
Public bug reported:
This happens with kubuntu jaunty desktop cd, at least with kvm-83 and
kvm-84. If kvm is started with the -vga std parameter (which is needed
for better graphics), xorg doesn't start. In /etc/X11/xorg.conf the
Driver line is incorrectly set to cirrus. Setting it to vesa solves
Here is my xorg.0.log
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/23512199/Xorg.0.log
--
x not starting in kvm with std vga
https://bugs.launchpad.net/bugs/338219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Update: another solution is simply to delete xorg.conf, but you'll get
only 800x600.
--
x not starting in kvm with std vga
https://bugs.launchpad.net/bugs/338219
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
36 matches
Mail list logo
