> if you didn't yet upgrade from an earlier focal version, make sure
that you remove the libcrypt1 package before the upgrade. Then do a
normal upgrade.
You say that like it's a fact but I just tried to upgrade from disco to
eoan to fossa and have this issue it seems.
Also, I can't fix this, my
I managed to purge this package with
sudo dpkg --purge --force-all linux-image-extra-4.10.0-35-generic
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED
linux-image-extra-4.10.0-35-generic
0 to upgrade, 0 to newly install, 1 to remove and 70 not to upgrade.
6 not fully installed or
Public bug reported:
`ubuntu-bug linux`
> Problem in linux-image-4.13.0-12-generic
> The problem cannot be reported:
>
> This is not an official Ubuntu package. Please remove any third party package
> and try again
```
cat /proc/version_signature
Ubuntu 4.13.0-12.13-generic 4.13.3
```
This
I'm also trying to run 16.10 desktop Ubuntu on a P651rp6-g laptop and
I'm experiencing the same issue. I have MSHYBRID option selected in the
UEFI, I'm using the UEFI rather than legacy Bios.
I'm currently using two ppas, the https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa with
I am similarly affected by this issue, we have a large number of
Chromecasts on our network, v1 and v2 and whilst the previous version of
Chromium worked just fine with the plugin installed this new version is
broken in some regard.
google-chrome-stable 53.0.2785.101-1 package does work, however.
I'm experiencing the same problem on Ubuntu 10.10 x64 (upgraded from 10.04).
This is a native install not through VirtualBox.
Basically any keys that are mapped in combination with super (win) are
triggered. It seems like the super key is stuck on.
e.g.
typing d - win+d (show desktop)
typing
Just updated my Ubuntu install to 9.04 and linkedin.com still times out when
posting data.
Tested with Firefox 3.0.8 DLink DSL - G604T.
--
linkedin very slow on Firefox Linux only
https://bugs.launchpad.net/bugs/314713
You received this bug notification because you are a member of Ubuntu
Bugs,
Interestingly the same laptop works perfectly when using the internet
connection at work (Ubuntu 8.10, Firefox).
So it must be some networking class between Ubuntu, DLink and LinkedIn.
--
linkedin very slow on Firefox Linux only
https://bugs.launchpad.net/bugs/314713
You received this bug
Networking 'clash' not 'class'.
--
linkedin very slow on Firefox Linux only
https://bugs.launchpad.net/bugs/314713
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I'm experiencing the same problem. Linkedin.com is incredibly slow.
The home page loaded fine, but clicking 'Sign in' takes forever. Once
I'm logged in, navigating around is works slowly, but if I edit some
data and submit the form it often times out.
The problem occurs in Firefox 3.0, Firefox
I'm guessing its related to: http://labs.alfaiati.net/guake/ticket/76
--
Changing Keyboard Shortcuts always ads +Mod2+ and does not work at all.
https://bugs.launchpad.net/bugs/291049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same problem here. Turning off Num Lock when changing the keys is a
work-around.
--
Changing Keyboard Shortcuts always ads +Mod2+ and does not work at all.
https://bugs.launchpad.net/bugs/291049
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The computer I had this problem with has since been decommissioned, so
I'm happy to have this issue closed.
--
Computer doesn't power off after shutdown (Feisty)
https://bugs.launchpad.net/bugs/96236
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm also getting the same problem as Nizar K on hardy.
--
miro.real crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/145413
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I haven't tried this in Gutsy yet, I'm going to wait until it is
released on the 18th then do a clean install. I'll post my results
then.
--
Computer doesn't power off after shutdown (Feisty)
https://bugs.launchpad.net/bugs/96236
You received this bug notification because you are a member of
I have updated my BIOS to the latest (1006) from ASUS for my A7S333 motherboard
by following this guide:
http://gentoo-wiki.com/TIP_Boot_Floppydisk_Image_without_Floppy_using_GRUB
I then added acpi=force to the kernel boot options:
title Ubuntu, kernel 2.6.20-15-generic
root
To move from the 386 to the generic kernel I used synaptic. I marked all of
the 386 kernel packages for removal, then rebooted the machine.
So I am now running the generic kernel, however the computer does not power
off, just like the 386 kernel.
Could it be something to do with the way the
I was unaware that the generic kernel is a more specific kernel than
i386. I am now running the generic kernel as my preferred kernel, so
this bug isn't so important to me now. I'm not sure why I ended up with
the i386 kernel when I upgraded from edgy to feisty, I'm sure I was
running the
Looks like the power off failure for 2.6.20-12-generic was a one off, it has
been working flawlessly since.
I reinstalled the 2.6.20-12-386 kernel and it won't power off, attaching the
relevant section of /var/log/messages
messages.txt covers:
1) Booting 2.6.20-12-386
2) Shutdown from GDM menu
Attaching dmidecode.txt
** Attachment added: dmidecode output
http://librarian.launchpad.net/7031362/dmidecode.txt
--
Computer doesn't power off after shutdown (Feisty)
https://launchpad.net/bugs/96236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Attaching /var/log/messages (showing boot, shutdown, boot)
It is the shutdown after 8am where the machine didn't power off.
** Attachment added: /var/log/messages
http://librarian.launchpad.net/7031377/messages.txt
--
Computer doesn't power off after shutdown (Feisty)
Attaching dmesg
** Attachment added: dmesg output
http://librarian.launchpad.net/7031365/dmesg.txt
--
Computer doesn't power off after shutdown (Feisty)
https://launchpad.net/bugs/96236
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Attempt to shutdown computer this morning and it didn't power off. This time I
was using the generic kernel (2.6.20-12-generic) which has previously always
turned off.
Attaching requested files...
** Attachment added: lspci output
http://librarian.launchpad.net/7031354/lspici.txt
--
Public bug reported:
When using the x386 kernel my computer does not power off when told to
shutdown. I tried the generic kernel and the computer shuts down normally (I
am currently running 2.6.20-12-generic). I experienced a similar problem in
Edgy.
If there is any other information you
25 matches
Mail list logo
