Now I am able to boot the loop device located on a windows (10) *NTFS*
partition:
laura@WUBI-UNITY:~$ sudo apt-cache policy initramfs-tools
[sudo] Passwort für laura:
initramfs-tools:
Installiert: 0.122ubuntu6~rc2
Installationskandidat: 0.122ubuntu6~rc2
Versionstabelle:
***
My interim solution to use '--- persistent' on a separate partition:
1. *rename* the partition 'casper-rw' into *system*
2. add a file 'casper-rw' of *0 Byte' into first/main *vfat* partition
3. add a new partition *home-rw* (optional)
4. on UEFI-computers add *persistent* to the first
Public bug reported:
After starting muon package the update and upgrade function is working
well.
But you can't never close the window, except using *systemmonitor*
(KSysGuard)
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: muon 4:5.4.3-0ubuntu1
ProcVersionSignature: Ubuntu
The Traceback on our computer differ to #3 as following, see last line:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in
_inline_callbacks
result = gen.throw(excep)
File
Some additional information:
root@USB-GNOME:~# efibootmgr
BootCurrent: 0002
Timeout: 1 seconds
BootOrder: 0002,0003,,0004
Boot* Windows Boot Manager
Boot0002* ubuntu
Boot0003* Trusty Thar
Boot0004* UEFI: SATA SSD S5FA
root@USB-GNOME:~# efibootmgr -v
...
Boot0002* ubuntu
It look to me, there are a missing funktion on some computers!
See my comment #6 - it has provided:
* Installing for x86_64-efi platform
On other computers I got it not :
root@KUBUNTU:~#apt-get upgrade
...
(Lese Datenbank ... 193730 Dateien und Verzeichnisse sind derzeit installiert.)
Sorry - I type to konsole:
root@KUBUNTU:~# apt-get upgrade
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Paketaktualisierung (Upgrade) wird berechnet... Fertig
Die folgenden Pakete werden aktualisiert (Upgrade):
No changes in the released fix of 25ubuntu1 - same information in the
boot screen!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464959
Title:
Secure Boot broken on amd64 with grub2 2.02~beta2-25
Now our solution - provided for *systemd* computers:
*/etc/fstab*
# LABEL=COMMON-SWAP none swapsw 0 0
uncomment swap-volume only!
*/etc/crypttab*
# target name source device key file options
cryptswap1 LABEL=COMMON-SWAP /dev/urandom
Stay with script for upstart version as provided with #32
Due to *systemd* will work no longer with *init.d* anyway.
The version #39 makes nothing else then to provide the *crysetup* in
background only.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yes this patch is working - but under *upstart* only.
Using the coming up systemd feature this patch will destroy more than
the patch helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1310058
Public bug reported:
After the Update of the package
* shim_0.4-0ubuntu5
the packages
* shim-signed_1.6+0.4-0ubuntu4
has been deinstalled due to wrong install recommandations of package
shim.
The packages must be adapted internal.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: shim
@ Albert - both options should be used alternatively only:
* offset=8
or
* skip=8
never both in one line.
for further Informations see man cryptsetup - options
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
We have installed ubuntu beta-64amd.iso (trusty tahr) as wubi on a
windows 8.1.
Since upgrade
* busybox-initramfs from 1.20.0-8.1ubuntu1 to 1.21.0-1ubuntu1
* busybox-static from 1.20.0-8.1ubuntu1 to 1.21.0-1ubuntu1
the wubi installation won't work / start and ends with the
** Attachment removed: system-informations.txt
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1317437/+attachment/4107931/+files/system-informations.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: boot.log
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1317437/+attachment/4108030/+files/boot.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1317437
Title:
wubi
** Attachment added: system-informations.txt
https://bugs.launchpad.net/ubuntu/+source/lupin/+bug/1317437/+attachment/4108031/+files/system-informations.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As workaround we inserted in the file 10_lupin - see last 4 lines:
**
if [ x$type != xrecovery ] ; then
save_default_entry | sed -e s/^/\t/
echo gfxmode \$linux_gfx_mode | sed s/^/$submenu_indentation/
fi
echoinsmod gzio | sed s/^/$submenu_indentation/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316968
Title:
grub-2 file 10_lupin wrong partition_table
To manage notifications about this bug go to:
** Attachment added: 10_lupin
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1316968/+attachment/4108086/+files/10_lupin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1316968
Title:
As workaround we inserted in the file 10_lupin this supplement below
line containing:
echo insmod gzio | sed s/^/$submenu_indentation/
*
host_device=$( mount | grep /host | cut -d -f 1 )
part_table=$( grub-probe --device $host_device --target=partmap )
if [ ! x$part_table =
Public bug reported:
Using the wubi trusty-thar (14.04 lts) installation, the upstart don't
finishes on a
* guid partition table formatted device / harddisk.
The package / files
* 10_lupin
* usr/share/grub/mkconfig_lib
generates while - sudo update-grub
(only relevant lines copied)
This bug was introduced by upgrade the packages
* busybox-initramfs
* busybox-static
from issue 1.22.0-5ubuntu1 to 1.22-0-6ubuntu1
Downgrade to the mentioned former version (anymore available in the archives,
but stored localy) or to 1.21.0-1ubuntu1 followed by
* sudo update-initramfs -u
With version busybox-1:1.22.0-5ubuntu1 fix has been released.
** Changed in: busybox (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1254428
Title:
A possible workaround inside the script /usr/bin/ecryptfs-setup-swap
could be:
***
# Add crypttab entry
echo cryptswap$i UUID=$uuid /dev/urandom
swap,offset=8,cipher=aes-cbc-essiv:sha256 /etc/crypttab
***
Please test the supplement offset=8 as a sufficient space to avoid the
UUID
Public bug reported:
After changing the the script
* /usr/bin/ecryptfs-setup-swap
* from old version with:
*
# Add crypttab entry
echo cryptswap$i $swap /dev/urandom swap,cipher=aes-cbc-essiv:sha256
/etc/crypttab
*
* into latest version with:
*
# Add
** Description changed:
After changing the the script
- * /usr/bin/ecryptfs-setup-swap
+ * /usr/bin/ecryptfs-setup-swap
* from old version with:
*
- # Add crypttab entry
- echo cryptswap$i $swap /dev/urandom swap,cipher=aes-cbc-essiv:sha256
/etc/crypttab
+ #
I dont think so ! The problems with the picture is solved.
Basic is a fresh installed trusty 'Kubuntu'.
grub-version after installation was 2.00-22
After the upgrade (activated proposed) grub packages 2.02~beta2-5 I got these:
* an additional folder 'grub' - see below
Upgrade of an older 'Ubuntu-GNOME' installation
* from 2.02~beta2-4 to 2.02~beta2-5
is working without any malfunction. No additional folder 'grub' has been
created, picture is show now inside 'grub-menu'
Again: in the 'Kubuntu' installation the
* 'nvram-entry' Boot* ubuntu
has been
Public bug reported:
Based on a fresh Kubuntu installation
* grub-version after installation was 2.00-22
After the upgrade (activated proposed) to grub_2.02~beta2-5 I got an
additional folder 'grub' and an additional entry inside the 'nvram':
The information to these folders inside directory
Done -
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1273694
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1269992
Title:
2.02~beta2 requires manual testing
To manage notifications
Next- During the upgrade on an older 'trusty-Ubuntu-Gnome' System inside a
terminal with
* sudo apt-get update
* sudo apt-get upgrade
the package upgrade
* from grub_2.00-22 to grub_2.02~beta2-5
hints. The files inside the folder '/boot/efi/EFI/ubuntu' are not updated
automatically.
Doing
See above - #2 is a trusty 'Ubuntu-GNOME' installation and there are no
'/etc/default/grub.d' folder either a 'hijacking'-file!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1273694
Title:
Yes deleting inside Kubuntu the folder '/etc/default/grub.d' solves it.
Forget my #4 - it will be my failure - I will look if there are former
changes in the installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hallo I'm back after a long periode of testing / investigations.
The problem is located inside 'secure-boot' !
Switching inside EFI-BIOS to 'non-secure-boot' option all works as
axpected.
It's not based in the form of picture (*.png either *.jpg).
Based on the output of grub-shell showing ever
** Attachment added: /boot/grub/themes/***/theme.txt
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956549/+files/themes-danmark-theme.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: /etc/default/grub
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956547/+files/etc-default-grub.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: /boot/grub/grub.cfg
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1269992/+attachment/3956548/+files/boot-grub-grub.cfg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The submitted '/boot/grub/grub.cfg' is the output of above '/etc/default/grub'
and will not work below
- grub 2.02~beta2-4
but without any restriction below
- grub 2.00-22
The '/boot/grub/themes/***/theme.txt' ist working with 'secure-boot'
witout restrictions on all systems.
--
You
Further no more working function found here - all relevant systems
after upgrade involved!
The background picture is stated in the '/etc/default/grub'
- GRUB_GFXMODE=1024x768
- GRUB_BACKGROUND=/usr/share/backgrounds/gnome/Stones.jpg
Both versions 2.00-22 as well as 2.02~beta2-4 output of 'sudo
Here it won't work:
tail of terminal output *
root@USB-GDM-TRUSTY:~# grub-install -v
line numbers for indification only
line 1 : grub-install: Info: the core size is 0x26978.
line 2 : grub-install: Info: writing 0x27c00 bytes.
line 3 : grub-install: Info: copying
Now I found the real brocken packages:
* busybox-initramfs
* busybox-static
both version of 1:1.21.0-1ubuntu1
Downgrading to the former packages version 1:1.20.0-8.1ubuntu1 lets
boot the system without any malfunction.
In accordance with the date of installation of the latest busybox
Public bug reported:
Startting a wubi-installation after the kernel-image has been managed by
* sudo update-initramfs -u -k 3.12.0-1
it is not possible to boot with these kernel-image. It ends in a
busybox. See also the Information given by the attachment
ProblemType: Bug
DistroRelease:
@ NikTh:
No these ist an older computer with basic operating system (at time)
* Ubuntu Precise Pangolin (12.04.3 LTS)
which has inside the grub.cfg an option to start two further ubuntu-OS as
wubi-installation (loop-devices) located on a seperate NTFS formated partition
for testing purposes
The same happens with the kernel image updated to
* 3.8.0-11_3.8.0-11-20
@Joseph: Your link to the images shows no installable kernel image(s) -
tested on march 6th 2013 - so requested test couldn't performed now.
Once more: Booting with the recovery, you will reach the recovery
console.
Public bug reported:
Notice: These bug is shown in the installer used in quantal quetzal
only
During installation with / on an EFI-System gpt is used, partition
table of the installer proposes for the type of partition
- primary
- logical
but both buttons are useless and should be
The question isn't how to do the work-around!
It must be implemented inside the script 10_linux (or other one), so
it's a fixed part independent of the users knowledge.
It is right to use/set the definition of users only!
--
You received this bug notification because you are a member of
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920955
Title:
gnome-codec-install uses wrong package architecture
To manage notifications about this bug go to:
Public bug reported:
After installing a new amd64 64bit system and and starting the videoplayer
totem the automatic
codec-install
appears and installed after approval nessassary codecs - but the wrong
architecture - all packages are signed ***:386 and I could't use the
videoplayer as
*** This bug is a duplicate of bug 918657 ***
https://bugs.launchpad.net/bugs/918657
** This bug has been marked a duplicate of bug 918657
unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@*Michael Terry*
Please consider, that all positions mentioned (~.drmc as well as
gsettings) are not readable, if you are using an encrypted home
(ecryptfs).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/918657
Title:
unity-greeter_0.2.0-0ubuntu2 breaks desktop-selector
To manage notifications about this bug go to:
Public bug reported:
After updating the package unity-greeter
from version 0.1.1-0ubuntu1 - to version 0.2.0-0ubuntu2
I can't select any other desktops - it starts with the former selected
unity 3D only.
Available desktops are:
GNOME (3), TERMINAL (1), UNITY, UNITY-2D
Downgrading to the
Supplement:
This happens on a single-user-system only and if the option of
/etc/lightdm/lightdm.conf
allow-guest=false
is set. If the guest-account or an additional user is available,
then by changing the user the desktop-selector will be shown!
--
You received this bug notification because
Additionally the background of the root-terminal (/usr/bin/x-terminal-
emulator) is involved in the same manner.
Depending the theme, it could happen, no character could be read
anymore.
For me it's a bug, too!!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914620
Title:
update-manager ignores blocked packages
To manage notifications about this bug go to:
Public bug reported:
I have blocked some packages using synaptic, to avoid an update or
usage. Due to test the functions, only.
These packages are brltty, ubuntu-desktop and some others. I
deinstalled them and blocked them.
But after starting the update-manager from panel-menu, I get an
I reinstalled the aptdaemon set of packages (now version +bzr756)
too and can cofirm that the U-M is running well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894671
Title:
update-manager freezes
On the URL following you will find the btrfs-tools version
0.19+2005-2
- http://packages.debian.org/en/sid/btrfs-tools -
(provided as *deb-package) which contains a lot of the features
requested. This should in minimum be integrated to the ubuntu-repos
next.
--
You received this bug
Today trouble-shooting results in:
- python-aptdaemon, python-aptdaemon-gtk, python-aptdaemon-gtkwidgets
and/or python-aptdaemon-gtk3widgets
are the faulty packages.
A downgrade to packages provided by precise-alpha1
(vers.:0.43+bzr712-0ubuntu1) or earlier oneiric-release (vers.:
What I noticed last - starting the update-manager gui and available
updates are shown (gathered otherwise, may be last run?).
Starting the update / upgrade directly with the button
- update now
it proceed without any delay. So I forced this circumstance by inserting
into the file
-
** Changed in: update-manager (Ubuntu Precise)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894671
Title:
update-manager freezes after initialization
To
Sorry - but the last days it works for me without restrictions - I can't
remember that I did additionally works on it.
Set back to confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894671
I've taken the syslog information during update-manager was running
(see attachment).
What I noticed is the gap between the timestamps:
- Dec 11 12:07:27 localhost anacron[905]: Job `cron.daily' started
- Dec 11 12:24:28 localhost anacron[905]: Normal exit (1 job run)
Behind this the update
The fix has been released with
- update-manager_1:0.155.1
- update-manager-core_1:0.155.1
** Changed in: update-manager (Ubuntu Precise)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
update-manager_1:0.155.1
update-manager-core_1:0.155.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894671
Title:
update-manager freezes after initialization
To manage notifications about this
After reading the comments, I can confirm, that the GUI of update-
manager, if using the gnome-shell first, it's working fine.
If starting with ubuntu-desktop the update-manager won't work and
freezes after pushing the button install updates.
Interupting, wait, logout and changing to the
Public bug reported:
After selecting SYNAPTIC from launcher and confirming authorization,
the GUI will appear and closes shortly.
This happens on several machines, i386- as well as on
amd64-architecture.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: synaptic 0.75.2ubuntu8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894662
Title:
Synaptic closes shortly after starting GUI
To manage notifications about this bug go to:
Public bug reported:
After starting the UPDATE-MANAGER from launcher and using the search-
button for updates, the GUI freezes after downloading the update-
informations. Starting the the start-update-button is not possible
anyway. These happens on several machines with i386-architecture as
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894671
Title:
update-manager freezes after initialization
To manage notifications about this bug go to:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/887589
Title:
wrong syntax in file /lib/recovery-mode/options/dpkg
To manage notifications about this bug go to:
Public bug reported:
Always using the Recovery_Modus and selecting inside friendly-
recovery-menu the option:
dpkg
you get the message:
Removing of /var/cache/apt/archives/partial/*“ not possible. File not
found
Removing of /var/lib/apt/lists/partial/* not possible. File not found
Caused to
No - it works without any restrictions - if you are using gdm, not
lightdm!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/426724
Title:
login-screen has no user-pictures with encrypted home
*** This bug is a duplicate of bug 862743 ***
https://bugs.launchpad.net/bugs/862743
Same happens to me.
This seem independent from graphic card - my graphic card is intel
integrated device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: grub2
The time to procede a sudo update-grub during an installation or
deinstallation a kernel is not acceptable long. This happens since
update to version 1.99-4ubuntu1. Additionally the CPU is running at 100%
the whole time.
Output terminal during
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/787461
Title:
sudo update-grub takes extremely time
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: /boot/grub/grub.cfg
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/718670/+attachment/1856563/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/718670
** Attachment added: custom.cfg (contains pbkdf2-parameter)
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/718670/+attachment/1856564/+files/custom.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Update and workaround:
I inserted manually into the grub.cfg between the lines:
submenu Previous Linux versions {
menuentry 'Ubuntu, mit Linux 2.6.37-12-generic' --class ubuntu --class
gnu-linux --class gnu --class os {
submenu Previous Linux versions {
set superusers='xxuser_namexx'
I provided a password-file containing:
### BEGIN 01_user_list ###
set superusers='xxuser_namexx'
password_pbkdf2 xxuser_namexx grub.pbkdf2.sha512.3.DC0E03A0DB4
### END 01_user_list ###
These file 01_user_list will be added into the grub.cfg during sudo
update-grub.
The file
** 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/718670
Title:
grub pbkdf2-function hints
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 625234 ***
https://bugs.launchpad.net/bugs/625234
You are the expert - I can see the results don't happen, only - never
writing the file grubenv.
--
grub2 function savedefault hints on LVM-devices
https://bugs.launchpad.net/bugs/560594
You received this
*** This bug is a duplicate of bug 625234 ***
https://bugs.launchpad.net/bugs/625234
** This bug has been marked a duplicate of bug 625234
Cannot save_env on LVM (vg_1-boot)/grub/grubenv
* You can subscribe to bug 625234 by following this link:
to fix this - search for file - /usr/lib/grub/grub-mkconfig_lib and
change:
go to line 45:
make_system_path_relative_to_its_root ()
{
${grub_mkrelpath} $1
}
to:
make_system_path_relative_to_its_root ()
{
path=`${grub_mkrelpath} $1`
# ${grub_mkrelpath} $1
}
and it seems to be working
Same to me!
Starting vmlinuz and initrd.img by using the grub-cmdline with the given
parameters starts without restrictions.
--
[natty] GRUB no longer finds kernel with separate /boot partition
https://bugs.launchpad.net/bugs/665471
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 665471 ***
https://bugs.launchpad.net/bugs/665471
** This bug has been marked a duplicate of bug 665471
[natty] GRUB no longer finds kernel with separate /boot partition
* You can subscribe to bug 665471 by following this link:
*** This bug is a duplicate of bug 661075 ***
https://bugs.launchpad.net/bugs/661075
** This bug has been marked a duplicate of bug 661075
unhandled exception
* You can subscribe to bug 661075 by following this link:
Jens Janssen wrote: The bug appears again under Ubuntu 10.10 beta.
I can't agree - due to the updates took place last days, the user
picture has been deleted meanwhile.
After reset -- System - Preferences - About Me -- User Picture
the user picture is shown again inside the login-screen
Public bug reported:
Binary package hint: grub2
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu 10.04.1 LTS
I installed my Lucid Lync inside a LVM-System with seperate (vg_1-boot)
and configured the
* /etc/default/grub
- GRUB_DEFAULT=saved
-
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/625234/+attachment/1522648/+files/Dependencies.txt
** Summary changed:
- Cannot procidesave_env on LVM (vg_1-boot)/grub/grubenv
+ Cannot save_env on LVM (vg_1-boot)/grub/grubenv
--
Cannot save_env on LVM
Public bug reported:
Binary package hint: grub-pc
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu lucid (development branch)
harddisk/partition = /dev/sdb /dev/sdc as RAID1
configured with LVM2 = '(vg_1-boot)', '(vg_1-root)', '(vg_1-home)',
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43766810/Dependencies.txt
--
grub2 function savedefault hints on LVM-devices
https://bugs.launchpad.net/bugs/560594
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: grub.cfg
http://launchpadlibrarian.net/43768724/grub.cfg
--
grub2 function savedefault hints on LVM-devices
https://bugs.launchpad.net/bugs/560594
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: gnome-system-tools
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu lucid (development branch)
Linux LUCID-4G32R 2.6.32-16-generic-pae #25-Ubuntu SMP Tue Mar 9
18:03:39 UTC 2010 i686 GNU/Linux
all ubuntu (gnome
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41694842/Dependencies.txt
** Description changed:
Binary package hint: gnome-system-tools
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu lucid (development branch)
** Attachment added: lspci -vnvn (plaintext)
http://launchpadlibrarian.net/39238181/lspci.txt
--
failed to allocate wireless device
https://bugs.launchpad.net/bugs/404596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The performance is unchanged - with the latest kernel too.
The supplement at the end of the kernelline pci=use_crs helps as in
past.
Added logs: dmesg + lspci -vnvn (both as plaintext)
** Attachment added: dmesg (plaintext)
http://launchpadlibrarian.net/39238165/dmesg.txt
--
failed to
Same bad experiences with the i386-kernel 2.6.33-020633rc8
--
failed to allocate wireless device
https://bugs.launchpad.net/bugs/404596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Directed to the main package.
** Package changed: ubuntu = ecryptfs-utils (Ubuntu)
--
9.10 karmic gdm login fails after changing password (users-admin) when home
folder encrypted (ecryptfs)
https://bugs.launchpad.net/bugs/470129
You received this bug notification because you are a member of
1 - 100 of 196 matches
Mail list logo
