it just boots straight into Windows)
It's different when I shut down Windows 8 and then boot the non-Wubi install
(12.04.1). Then when I try to mount the windows partition I get:
bcbc@neptune:~$ sudo mount /dev/sda1 /mnt
Windows is hibernated, refused to mount.
Failed to mount '/dev/sda1
For a Windows 8 shutdown and booting (non-wubi) Ubuntu, I get:
bcbc@neptune:~$ head -c 30 '/mnt/$LogFile' | tail -c 4 | od -t x1
000 00 00 02 00
004
But it won't mount it, except read-only so, in that sense, it's safe.
But it would be a pain for a user trying to boot from an Ubuntu USB
** Package changed: ubuntu = ubuntustudio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070682
Title:
wubi and ubuntu studio
To manage notifications about this bug go to:
An update on this bug... I have two raring installs. For one of them the
brightness controls work, one doesn't.
The one that doesn't work is a vanilla upgrade to Raring 13.04 from
Quantal 12.10.
The one that works is also an upgrade from 12.10, but there are two major
differences:
1. I
** 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/980338
Title:
gcompris crashed with SIGABRT in mem_error()
To manage notifications about this bug go to:
Retested this. The problem doesn't occur on 12.10 or 13.04.
It still happens on 12.04.2, which is using with nautilus 3.4.2.
Actually 12.10 is also using nautilus 3.4.2. So maybe this isn't a
nautilus bug after all. In 12.04.2 the window pops up but nothing
changes in the Unity bar.
In 12.10,
Just noticed my brightness controls are working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1105604
Title:
Brightness control stopped working
To manage notifications about this bug go
Here is another: http://askubuntu.com/questions/269720/cant-start-
windows-after-installing-ubuntu
And another:
http://ubuntuforums.org/showthread.php?t=1769482p=12560337viewfull=1#post12560337
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: grub2 (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079482
Title:
Windows 7 Not Booting after Grub installed to bootsector
To manage
Grub2 was fixed to prevent offering to install on any windows partition. This
seems to be a regression if it's offering Windows partitions now. I've noticed
a couple of similar cases on askubuntu.com:
http://askubuntu.com/questions/230775/problem-with-dual-boot-windows-xp-ubuntu-12-04
Here's the bug I was referring to: bug 576724
This is a comment from that bug:
This bug was fixed in the package grub2 - 1.98+20100614-2ubuntu4
---
grub2 (1.98+20100614-2ubuntu4) maverick; urgency=low
* Rearrange postinst install_devices logic so that preparatory code is run
PS here is another one: http://askubuntu.com/questions/263606/windows-8
-no-longer-boots-after-grub-wiped-out-the-windows-bootsector
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079482
Title:
Phillip Susi,
There seem to many a number of issues here, but the fact is that Grub
installed itself over the windows boot sector, not the MBR. Wiping out
the partition boot sector prevents Windows from booting, whereas
replacing the bootloader in the MBR is normal (obviously). The bug I
reported
Now on Raring, the backlight is off after resuming from suspend. I have to run
the following (blind type) after resuming each time:
echo 978 | sudo tee /sys/class/backlight/intel_backlight/brightness
Also, the function keys to control the brightness setting still don't
work. They do on Quantal.
Here is the syslog during the suspend/wake. This maybe a separate bug...
but will move later if nec:
Mar 8 18:49:30 malraux kernel: [ 593.626366] composite sync not supported
Mar 8 18:49:31 malraux kernel: [ 593.787884] composite sync not supported
Mar 8 18:49:31 malraux
Latest update... the brightness control keys 'work'. The slider moves up
and down, but there is no impact to the actual brightness. I'm
controlling the brightness manually by setting it automatically after
bootup and resume|thaw via scripts.
I'm running raring with the Mir ppa, but I have another
** Summary changed:
- Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
** Description changed:
I first noticed this behaviour in Ubuntu 11.10. When
I think this is a Unity action, not Nautilus
** Package changed: nautilus (Ubuntu) = unity
** Summary changed:
- Unable to open a folder for 10 GB Filesystem, No application is registered
as handling this file... Nautilus pops browser on bash partition mount
+ Unable to open a folder for 10 GB
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bcbc 1914 F pulseaudio
Date: Sun Jun 30 21:23:54 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=9b959dc9-7784-4b26-8506-ca98c00a5eb8
InstallationDate
I haven't yet been able to duplicate the kernel oops.
I can get the computer to Suspend while Shutting down on the latest
Ubuntu kernel, and I get the same behaviour using the Mainline build,
but so far no kernel oops.
Reproducible:
If I shut the lid immediately after shutting down, it proceeds
** Package changed: ubuntu = wubi
** Changed in: wubi
Status: Confirmed = 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/1134770
Title:
Wubi fails to detect 12.04.2 and 13.04
Public bug reported:
After today's update my brightness controls aren't working anymore.
After checking the System Settings, Brightness and Lock there is no
longer any brightness slider bar shown for manual setting either. So my
screen is fixed on full brightness.
The same thing happened during
I downgraded to confirm the old version was working (it was). Upgraded
again and this time the Fn keys weren't working, but the brightness
slider was present. There is also so much general instability (multiple
crash reports and lockups) I couldn't confirm that the problem is
related to g-s-d.
--
This has been happening to me for a couple of weeks. Raring is unusable
with continual crashes. If there's any info I can contribute, please let
me know. I'm running a Dell Inspiron N4010 with an Intel Arrandale gpu.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Just ran latest raring updates. Screen on full brightness, Fn keys
didn't move the slider. Going to the Brightness settings I can move the
slider but it has no effect.
Setting it manually still works: echo 978
/sys/class/backlight/intel_backlight/brightness
ProblemType:
Bug 541595 is marked as 'fix released'. So it's no longer active. Also,
that bug was to do with an incorrect report that a package was already
installed. The other bug 996379 is marked as invalid.
This bug is to do with update-manager checking the space required for
the release-upgrade
*** This bug is a duplicate of bug 1009247 ***
https://bugs.launchpad.net/bugs/1009247
** This bug has been marked a duplicate of bug 1009247
Windows installer (wubi.exe) download link doesn't work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I ran a wubi upgrade from 10.04.4 to 12.04. I created a separate bug
report for the upgrade in bug 984593. I guess some of the errors I saw
are reporting themselves ;) so I'll pass them on
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: memtest86+ 4.20-1.1ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984598
Title:
package memtest86+ 4.20-1.1ubuntu1 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
Public bug reported:
Upgraded a wubi install from 10.04.4 to 12.04. I reported the errors
(and attached logs) in bug 984593. This is one of those errors that is
self-reporting.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: friendly-recovery 0.2.25
ProcVersionSignature: Ubuntu
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bcbc 1752 F pulseaudio
Card0.Amixer.info:
Card
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984601
Title:
package friendly-recovery 0.2.25 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/984599
Title:
package linux-image-3.2.0-23-generic 3.2.0-23.36 failed to
install/upgrade: ErrorMessage: subprocess installed post-installation
*** This bug is a duplicate of bug 984474 ***
https://bugs.launchpad.net/bugs/984474
** 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/984602
Title:
initctl
Joseph Salisbury,
The bug is about an error I received during the upgrade from 10.04.4 to 12.04.
As I said in the description, the error was likely false, since the upgrade
worked (and the kernel booted fine). I was testing the Upgrade process at the
time (it's a throwaway install). So I'm not
Public bug reported:
I first noticed this behaviour in Ubuntu 11.10. When I run my bash
script that mounts partitions on my hard drive (e.g /dev/sda5), Nautilus
pops up with a browser window. This is an illogical action, since I've
not 'inserted a drive', it's already there, and it's just been
Public bug reported:
I ran an upgrade from 11.10 to 12.04 with 1.9GB free space. No warning
was given about insufficient free space. I received two popup windows
during the upgrade informing me that I was low on space and this went
down to less than 100MB (as I manually freed up space).
The
** Attachment added: dist-upgrade.zip
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/986272/+attachment/3096685/+files/dist-upgrade.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
2012-04-18 22:18:42,171 DEBUG Free space on /: 1856667648
2012-04-18 22:18:45,900 DEBUG dir '/var/cache/apt/archives' needs '987733436'
of 'DistUpgradeCache.FreeSpace object at 0xae731cc' (1856667648.00)
2012-04-18 22:18:45,901 DEBUG dir '/usr' needs '211730432' of
Okay, I hadn't noticed (or heard about) the bit about 'hybrid sleep'.
I switched it on, used the sleep, and then woke up from the sweep.
Then I hit Restart and tried to boot into Wubi, but it didn't work. I can't
mount the windows partition except in read-only mode.
bcbc@neptune:~$ head -c 30
I still fail to see why this is a bug in wubi or ntfs-3g. The way I see it is
that Windows8 chooses to hibernate by default on shutdown (unless fast-start is
disabled), without the knowledge of the user. The fact that the user is unaware
of it, doesn't change the fact that it's hibernated. So
Elijah, open a new issue or look for an existing issue e.g. I think bug
776590 covers this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/947748
Title:
Brightness control not working after
This historically happened with the ubuntu installer (ubiquity) if parted
returns errors (both normal and wubi installs). Seen it before when there
is leftover GPT data on a MBR formatted disk. Try booting from the USB and
going to a terminal (or hit Ctrl+Alt+F1 during the installation) and run:
Same thing happened to me. I just did a test 14.04 install on the same
computer so it's not a local issue.
The Fdisk output is odd - looks like it's trying to partition the 6GB
root.disk so that it has an efi partition:
Disk /dev/loop0: 1.1 GiB, 1162936320 bytes, 2271360 sectors
Units: sectors
** Attachment added: /var/log/installer/debug
https://bugs.launchpad.net/wubi/+bug/1385930/+attachment/4249641/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385930
Title:
14.10
** Branch linked: lp:~noorez-kassam/ubuntu/utopic/initramfs-tools/fix-
for-1317437
--
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 kernel option rw required
To manage
No I haven't seen this again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980338
Title:
gcompris crashed with SIGABRT in mem_error()
To manage notifications about this bug go to:
201 - 247 of 247 matches
Mail list logo
