Same here on 17.04. I cannot actually use the Dropbox icon from the indicator
panel as it doesn't display a menu, but rubbing nautilus --no-desktop open a
single nautilus window but kills the desktop.
If I subsequently run nautilus from Alt-F2 I get:
(nautilus:5292): GLib-GIO-CRITICAL **:
g_dbus
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633826
Title:
nautilus desktop crashes when called with --no-desktop
To manage
I am definitely running a 2.6.22-14-generic on an iMac 24"
Linux 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
Just upgraded to Gutsy and sound didn't work (as it didn't work in Feisty
without patching alsa). Installed linux-backports-modules, rebooted, and sound
worked
-
installing linux-backports-modules solves the issue
--
2.6.22-14 Sound does not work on iMac (Intel first Gen) REGRESSION
https://bugs.launchpad.net/bugs/154411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
** Changed in: linux-source-2.6.22 (Ubuntu)
Status: New => Confirmed
--
2.6.22-14 Sound does not work on iMac (Intel first Gen) REGRESSION
https://bugs.launchpad.net/bugs/154411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Confirmed here too.
My solution has been adding:
udevsettle --timeout=10
in /usr/share/initramfs-tools/init before line:
log_begin_msg "Mounting root file system..."
and then rebuild initrd with:
sudo update-initramfs -u -k all
I believe thi is the right way to go, as it guarantees that udev
Try adding
udevsettle --timeout=10
in /usr/share/initramfs-tools/init before line:
log_begin_msg "Mounting root file system..."
and then rebuild initrd with:
sudo update-initramfs -u -k all
--
[feisty] intermittent dropping to init shell
https://bugs.launchpad.net/bugs/99439
You received thi
Even without LVM "ln /dev/md0 /dev/md/0" satisfies the installer, so
that i happily arrives to completion, but the system doesn't boot, it
throws you to a (frozen? or is it my USB keyboard?) busybox shell with
error "/bin/sh:can't access tty; job control turned off"
--
/dev/md0 construct not sup
...but if your root is on a raid volume your system is unbootable,
dropping you to an unresponsitive busybox with error "/bin/sh:can't
access tty; job control turned off"
--
raid assembly breaks on pre-existing arrays
https://launchpad.net/bugs/84679
--
ubuntu-bugs mailing list
ubuntu-bugs@list
