This bug is not valid.
Found is UbiquitySyslog: E: Failed to fetch cdrom://Ubuntu 14.10 _Utopic
Unicorn_ - Release amd64 (20141022.1)/pool/main/g/grub2/grub-efi-
amd64-bin_2.02~beta2-15_amd64.deb Hash Sum mismatch
Event though I had reformatted the installation usb stick before burning
the
Public bug reported:
Asus X551-MAV-EB-01. Fast boot and secure boot are disabled. CSM is
enabled.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubiquity 2.20.0
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
** Attachment added: cups-browsed.conf
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1431366/+attachment/4357513/+files/cups-browsed.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did a fresh install, then manually upgraded packages in the dist-
upgrade one by one to isolate the ones pulling in fcitx.
indicator-keyboard did not pull in fcitx. It was unity-control-center
and unity-settings-daemon that are each trying to pull in the fcitx
packages.
--
You received this
Public bug reported:
Received the newest update to 0.0.0+15.04.20150310 a few minutes ago.
There is a significant change to behavior with the change to fcitx from
ibus.
Users, however, are given no warning and no instructions on how to get
their preferred input methods set up again.
This has
Thanks for your quick response.
I was running Vivid on 2 laptops. I did a dist-upgrade on each of them
and had the experience described above on both laptops.
Additional details:
1. ibus and ibus-pinyin were installed during system installation as
normal.
2. I added and then removed
I've already removed all fcitx packages except fcitx-data, libfcitx-
config4, libfcitx-glient0, libfcitx-utils0 (all required by Unity
Control Center, as you know) and reset the system IM back to Ibus; so
I'm back to normal.
I didn't really question the fcitx packages in the upgrade since it's
Additional information:
1. Before the 3.10.x line, the computer required hpet=disable
highres=off nohz=off in order to resume.
2. With the 3.10.x kernel, suspend/resume worked out of the box.
3. Suspend/resume still works with Debian Sid (3.16.x) and Fedora 21
(3.17.x).
4. The grub command
Public bug reported:
Computer would not resume after using suspend fn key. Computer would
sometimes think wifi was blocked by hardware switch after this. Had to
pull cmos battery to restore. This seems to be a regression to behavior
that went away with the 3.10 kernel.
ProblemType: KernelOops
Public bug reported:
Release 14.10; Ubiquity 2.20.0
Using manual partitioning on an Asus X201E (efi), I mounted a pre-
existing partition to be formatted as root. After clicking Install Now,
I got the warning dialog that is typical when installing Debian that
both the / partition and the swap
** Summary changed:
- Manual partitioning shows Debian dialog about formatting partition mounted as
root and swap
+ Manual partitioning shows Debian dialog about formatting partitions mounted
as root and swap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This change fixed the bug for me. Installed version: unity-control-
center 14.04.3+14.04.20140604-0ubuntu1
Test case:
1. Used unity-control-center to configure a user to log in without password.
User was added to the nopasswdlogin group and was able to log in without
password.
2. Used
Public bug reported:
Ubuntu has changed how it handles input switching and no longer relies
on the Ibus hotkey/trigger settings. The default upstream Ibus
keybindings for input switching, however, are still installed unchanged
in Ubuntu.
As a result, Control+Space, the default Ibus keybinding
Public bug reported:
If a user is set to login without a password and subsequently the
account is disabled, the user is not removed from the nopassword login
group. The result is that the user can still login even though the admin
has disabled to account.
This is a security issue and is present
After additional research, I realized that this bug is invalid against
accountsservice.
Instead, the bug is in Unity-Control-Center, which fails to change the
login mode when locking an account. A user who is already in the
nopasswordlogin group, therefore, will not be dropped from the
This bug seems to have been resolved. See Amal's comment that additional
updates took card of it for him. Plus, when I did another install, the
same updates/upgrades came through without causing a problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thank you for the reply. I agree that the line is in fact correct. I see
I mistakenly thought the mode had already changed, but that is not done
until after exiting the current block.
But here is how the bug is working:
Setting the mode to none causes the user to be added to the
nopasswdlogin
Public bug reported:
Update manager offered a partial upgrade, including Kernel 3.13.0.22.26
and removal of packages related to UbuntuOne. After starting the
upgrade, update manager showed a dialog stating You don't have
permission to perform this action. The upgrade continued after clearing
the
After a fresh install and apt-get upgrade, packages left for dist-
upgrade were:
The following packages will be REMOVED:
ubuntu-sso-client-qt ubuntuone-control-panel-qt
The following NEW packages will be installed:
libcgmanager0 liboxideqt-qmlplugin liboxideqtcore0 libwayland-egl1-mesa
After using a series of apt-get upgrade and apt-get install in order to
avoid using dist-upgrade, I was able to perform all of the
installs/removals/upgrades without causing the problem with user
authentication.
Very similar reports are starting to show up on AskUbuntu. It seems that
doing the
Additional note: The system drop-down under the gear icon did not show
me as logged in when I was. This would explain the failure of the gui
function to authenticate me, but I'm still not sure what caused that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Package changed: ubuntu = update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1302840
Title:
Upgrade in 14.04 causes admin user to not be recognized
To manage notifications
This bug is still present in 14.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169054
Title:
Disabling then Re-Enabling login without password does remove user
from nopasswdlogin group
To
This bug title is worded incorrectly. More accurate would be:
Changing user setting in User Accounts from Login without password to
Disable this account does not remove the user from the nopasswdlogin
group.
The user remains in the nopasswdlogin group only when going from Login
without password
Thank you for the quick reply.
I had in fact created a new partition table on that usb and made a new
partition before burning the iso, but something must have gone wrong or
perhaps there is another problem with that usb.
I reformatted a different usb for the installer and this time the
install
I managed to install 14.04 by creating a separate /boot partition. I
still got the error message that grub-efi-amd64-signed failed to
install; but opening gparted before closing the installer, I notcied the
/boot had about 150 MB on it.
The system EFI boot menu does not show any entry for 14.04,
This is an Asus X201E that came with 12.04 as an OEM install. There are
(presumably) no issues with Windows EFI involved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1299309
Title:
grub2 efi
I tried again and looked at /var/log/syslog before closing the
installer. It states there was a hashsum mismatch when it tried to
install grub-efi-amd64-signed_1.32%2b2.02~beta2-7_amd64.deb (may not be
the exact deb name) from /cdrom.
--
You received this bug notification because you are a
Public bug reported:
no additional info
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.17.10
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CasperVersion: 1.339
Date: Fri Mar 28
@dimistris-ha
I believe the options you list are for the 2.6 kernel. My S10-3 only
suspends and resumes when I use:
hpet=disable highres=off nohz=off
I have this set in Ubuntu 12.04 (kernel 3.2.x), Ubuntu 13.04 (kernel
3.8.x), and openSUSE 12.3 (kernel 3.7.x).
--
You received this bug
I continued to have this problem on my S10-3 running 12.10
3.5.0-21-generic. I installed 3.8-rc2 i386 from http://kernel.ubuntu.com
/~kernel-ppa/mainline/v3.8-rc2-raring/ and suspend now works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tried suspend/resume several times before adding the comment, but then
realized I woke it up right away every time. After some more attempts, I
realized that it's still not working right. It no longer freezes on
resume, but now it is not staying asleep. After suspend, it wakes up a
second or two
*** This bug is a duplicate of bug 1071301 ***
https://bugs.launchpad.net/bugs/1071301
** This bug has been marked a duplicate of bug 1071301
Can't change the desktop environment in lightdm when more than one desktop
is installed and the ok button is outside the visible screen.
--
You
Public bug reported:
12.10
unity-greeter 12.10.4-0ubuntu5
I expected an easy choice of desktop session after installing multiple
desktop environments. Instead, making a choice is very difficult.
The list of available desktop environments in unity-greeter does not
resize itself or provide easy
a dialog popped up titled update information (?) showing only the
string (null)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1064545
Title:
package-data-downloader crashed with KeyError in
Public bug reported:
12.04
ubuntu-restricted-extras 57
expected ms font package to install
ms font package did not install
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: ttf-mscorefonts-installer (not installed)
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994337
Title:
package ttf-mscorefonts-installer (not installed) failed to
install/upgrade: subprocess new pre-installation script returned error
37 matches
Mail list logo
