Work around:
Add a keyboard shortcut key:
Tools - Customize... - View - Freeze Window
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/760879
Title:
Window menu is hidden
To manage notifications
It is not just booting from a software raid, I have never tried that.
For me, it was enough that I had a software raid in my computer. I was
booting from an SSD.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Ran a normal
sudo apt-get update sudo apt-get upgrade
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: monodoc-base 2.10.8.1-1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/945588
Title:
package monodoc-base 2.10.8.1-1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Public bug reported:
After sudo apt-get update, I have to manually remove the
/var/lib/dpkg/lock file to be able to run sudo apt-get upgrade.
Actually it seems I must remove the lock file after running any apt-get
command.
A list of other running processes (ps ax) is found at pastebin:
** Summary changed:
- Must manually remove
+ Must manually remove /var/lib/dpkg/lock
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/943144
Title:
Must manually remove /var/lib/dpkg/lock
To manage
It seems like only apt-get is affected. Both aptitude and dpkg -i seems
not to be affected. Also apt-get seems to work if I wait some time
between the update and upgrade command.
worked:
aptitude update
aptitude upgrade
worked:
dpkg -i package.deb
--
You received this bug notification because
It does not fail all the time. It fails sometimes, and it seems to be
random. I do not know of any processes that used dpkg while apt-get was
failing and the output of lsof | grep /var/lib/dpkg did not return any
output.
I will update the bug report if the behavior continues and I discover
Public bug reported:
Happens at once on boot.
I happened to use the kernel 3.0.0-17, because the computer would not boot
because of the bug that the line
udevadm settle
is missing in function degraded_arrays() in the file
/usr/share/initramfs-tools/scripts/mdadm-functions which results in a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942106
Title:
update-manager crashed with ValueError in ./xorg_fix_proprietary.py:
_system not initialized
To manage notifications about this bug go
This bug still haunts natty, which still has indicator-datetime 0.2.3.
Is there any hope for the fixed package finding its way into natty-
updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774071
Making /usr/sbin/bluetoothd suid root, solves this problem, but might
pose some security issues.
sudo chmod +s /usr/sbin/bluetoothd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/762964
Title:
Had this problem for this device: ID 413c:8103 Dell Computer Corp. Wireless 350
Bluetooth
The suid root fix above solved this problem on the release version of Ubuntu
11.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the info Loye Young.
Some additional information:
The password for the oem account should be the same as the username,
oem.
I think you also need to run these commands:
You might have to remove the old users files
#rm -r /home/olduser
Add the oem user to the sudoers list.
# adduser
Further investigation turns out, it doesn't connect to eduroam on a
liveusb version of Lucid either.
I have attached dmesg prints, iwlist scan results and the certificate
for my network.
** Attachment added: files.tar.bz2
I can confirm having this bug on a fully updated Maverick. I tried using
three different network cards, none were able to connect to my schools
WPA2 Enterprise network (eduroam). The network uses PEAP and MSCHAPv2.
The network cards I tried are using the modules: ipw2200, p54 and ath9k.
I am
16 matches
Mail list logo
