Hi Nathaniel - have you tried my suggestion in
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/595648/comments/19
? i.e. just kill pymouth and then echo the password to passfifo as
normal
This still works for me in 14.04. I haven't needed to do any of the
other suggested patches or
Thanks Juha
I didn't notice there were two different options used for the session
(user-session and autologin-session). Using autologin-session=XBMC
works. I guess I didn't notice autologin-session because when you use
autologin-user without autologin-user-timeout then the user-session gets
used.
Hi Robert
That bug seems to be for lightdm-gtk-greeter. I'm using unity-greeter
and timed login does not work.
Config:
[SeatDefaults]
#user-session=ubuntu
user-session=XBMC
greeter-session=unity-greeter
autologin-user=xbmc
autologin-user-timeout=10
When I comment out autologin-user-timeout auto
Hi
I'm using x64 12.04 upgraded to the latest version from the repository.
1.2.3-0ubuntu1 is installed and auto login doesn't work when using
autologin-user-timeout. If I comment out autologin-user-timeout then it
will auto login (but of course it doesn't wait at the log in screen)
Config:
The following solution is simple and works for me. My configuration is
the default encrypted LVM setup created by the Precise alternative
installer.
ssh to the remote machine and run the following commands:
kill $(pidof plymouthd)
# Wait a few seconds for '/scripts/local-top/cryptroot' to
** Changed in: cryptsetup (Ubuntu)
Status: Triaged = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595648
Title:
Remote unlocking not possible if plymouth is active (Bug or
This bug appears to be in Qantal. I get this error from fail2ban:
Warning: The 'unhide.rb' command gave an error:
/usr/bin/unhide.rb:130: warning: assigned but unused variable - exe
/usr/bin/unhide.rb:32:in `module:LibC': uninitialized constant
DL::Importable (NameError)
Hi Diego
I added service tftpd-hpa restart as an up line to eth0 and it
worked! Thank you very much.
But even better still you pointed me in the right direction to get to
the bottom of the problem. My interface file looked like this:
# The primary network interface
auto eth0
#up service
Hi Diego
I added service tftpd-hpa restart as an up line to eth0 and it
worked! Thank you very much.
But even better still you pointed me in the right direction to get to
the bottom of the problem. My interface file looked like this:
# The primary network interface
auto eth0
#up service
Thanks Diego
I've got start on runlevel [2345] in the /etc/init/tftpd-hpa.conf file
(thanks, I didn't know about that).
As far a I can tell my interface is up long before tftpd starts:
dmesg | egrep 'eth0|tftpd'
[1.669351] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1)
Thanks Diego
I've got start on runlevel [2345] in the /etc/init/tftpd-hpa.conf file
(thanks, I didn't know about that).
As far a I can tell my interface is up long before tftpd starts:
dmesg | egrep 'eth0|tftpd'
[1.669351] e1000e :00:19.0: eth0: (PCI Express:2.5GT/s:Width x1)
Hi
I have the same problem with Precise (tftpd-hpa version 5.2-1ubuntu1).
It seems exactly the same as #23 above.
status tftpd-hpa saying running when it definately isn't.
Diego, I don't really understand the 'change the condition' stuff you
mention. Would you be able to explain in reasonably
Hi
I have the same problem with Precise (tftpd-hpa version 5.2-1ubuntu1).
It seems exactly the same as #23 above.
status tftpd-hpa saying running when it definately isn't.
Diego, I don't really understand the 'change the condition' stuff you
mention. Would you be able to explain in reasonably
I'm using 0.2.22 and I still get the Failed to install bootloader
message.
usb-creator 2010-05-01 18:11:17,338 (DEBUG) install.py:72: install thread
source: /tmp/tmpK3SafI
usb-creator 2010-05-01 18:11:17,338 (DEBUG) install.py:73: install thread
target: /media/704F-FF0E
usb-creator 2010-05-01
/transmissionrpc/transmission.py, line 86,
in __getattr__
raise AttributeError('No attribute %s' % name)
AttributeError: No attribute trackerStats
Expected output:
an integer
I have tried my test script with version 4.0 of transmissionrpc it works
correctly.
Regards
AllenS
** Affects: transmissionrpc
Public bug reported:
Binary package hint: rsnapshot
Please upgrade package to 1.3.1 (released 31 Aug 2008)
It fixes a number of bugs (as well as adding a few new features):
- Fix help message mixup in lines between -c and -t.
- Add more specific error messages for not currently implemented
That's bug #549247, already fixed in a newer version.
Sorry, that doesn't sound anything like what I get.
--
No graphical splash on VGA16fb (e.g., nvidia binary drivers), plymouth uses
text plugin (Ubuntu 10.04 in text)
https://bugs.launchpad.net/bugs/526892
You received this bug notification
Jacopo Moronato - I don't mind the 16 color too much, though it doesn't
look anywhere near as good as the Karmic splash with the proprietary
drivers. However, I only get the graphics on shutdown. The boot screen
is just black and white text (it was misaligned color text before I
updated to
Hi Steve. Thanks, but bug #549247 description is Notices/Warnings
during upgrade of plymouth (initramfs-hooks).
I had no problem 'during upgrade of plymouth' - my problem is at boot
time. I don't get any Notices/Warnings. Nor does this bug mention a
splash screen at shutdown. OK, to a developer
I've just picked up the latest update and I just get plain black and
white text when booting. Previously I got slightly garbled colored text,
not bitmaps.
I do get some graphics on shutdown - a graphical Ubuntu logo but it
looks wrong (could it be 8bit color?)
I use encrypted LVM. I get a plain
20 matches
Mail list logo
