Hooray Hooray.. problem # is 1607070. I hope that helps Sebastien.
The file did not allow read access, which caused the submit to fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606358
Title:
the file access was no read
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607070
Title:
additional crash file for 1606358
To manage notifications about this bug go to:
https://bugs.launchpad.net/u
Public bug reported:
attempting to provide the crash file for 1606358
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.14
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Archite
There is this guy..
http://askubuntu.com/questions/802468/menu-bar-and-launcher-missing-after-installing-updates-16-04-lts
which addresses virtualbox specifically.
It wouldn't submit, literally nothing happened. Now that was under a
16.04 image that was upgraded to 16.04.1.
When I did a fresh 16
This may actually be the same resolution as 1606358. I did see one
launcher icon 'vibrate' so, yes, the launcher is actually off screen.
Also,
http://askubuntu.com/questions/802767/16-04-1-upgraded-vm-cannot-access-
unity-bar-on-left-nor-move-desktop-windows
references this same problem. Does the
Sorry, I can NOT get it to submit.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606358
Title:
Ubuntu 16.04.1 unity disappears when set to autohide
To manage notifications about this bug go to:
ht
OK, I did describe two steps to reproduce. In the original case, it was
an existing 16.01 current with maintenance, that I in-place upgraded. As
it was existing I had already switched the launcher from autohide=off to
autohide=yes as well I already had a desktop icon. so there were two
artefacts of
I guess I don't understand your question concerning what I changed. My
change was to upgrade a perfectly good 16.04 image that functioned
perfectly and after the upgrade and subsequent reboot there was no
louncher and if I started Netbeans 8.1 (a desktop icon) or started a
terminal session, both wo
Public bug reported:
Initially I was going to report this against a completely working 16.04
VM using spice. In that case the system, once rebooted after the upgrade
failed to show launcher at all and no desktop applications could be
moved. This is new behavior in 16.04.1. All these things worked
I can no longer get a desktop login into my system. What can be done to
circumvent this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485277
Title:
unity-settings / compiz segfault and ui cras
Public bug reported:
This was part of an autoupdate and it failed on Aprinl 23 2014.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: mysql-server-5.5 5.5.37-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55
Uname: Linux 3.2.0-60-generic x86_64
NonfreeKernelModules
I had this problem with 12.04 on my laptop. After accepting an upgrade I
could no longer boot back in. I agree that acpi=off works solidly but,
from everything I've read, bad stuff can result. One thing I've noticed
myself as well as listening to others is you need to reboot several
times to be con
I believe there were several bugs open for essentially the same thing.
In my case if the partition was from a firmware RAID, grub wouldn't be
installed. I viewed this as a regression as originally, perhaps in the
7. time frame it didn't work with firmware raid unless one used the
alternate inst
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896658
Title:
unable to write bootloader on frosh install of 11.10 on firmware raid
5
To manage notifications about this bug go to:
https://bugs.launc
Public bug reported:
I had an existing 10.10 install on this very machine with firmware raid
0. I installed 4 500GB drives as raid 5 and the install worked right up
until the end when it failed.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ubiquity 2.8.7
ProcVersionSignature: Ubuntu 3.0.
Stephane - In my case the level was Natty and the target was a Dell
system with firmware RAID 1 against two 750 GB drives. It never wrote
grub out. I could not get install to install grub. I ended up having to
disable firmware RAID and fumbling through software RAID. Ubuntu has
supported firmware R
16 matches
Mail list logo
