I have this same issue; however, not caused by an upgrade to 9.10. Mine
is a fresh install of 9.10 (32bit), fully updated, to which I have added
several packages (work laptop rebuilt over the past 3 days).
Aptitude now wants to remove 100 packages (all listed with "{u}" after
their name), while ap
I am experiencing the same problem - however, the only statement I see in
syslog is a lot of:
Nov 26 12:23:14 soren-xps wpa_supplicant[1230]: CTRL-EVENT-SCAN-RESULTS
Posted this yesterday at ubuntu forums
(http://ubuntuforums.org/showthread.php?t=1337330) but guess I should
have checked here fir
Changing encryption from WPA2 to WPA seems to have fixed my issue (or
rather, appears to be a usable workaround - Obviously WPA2 is still not
working correctly.)
--
Ubuntu 9.10 Wireless Connection Intermittently Unresponsive
https://bugs.launchpad.net/bugs/453647
You received this bug notificatio
Indeed this was not a bug with Synaptic for me. Rather it turned out
that it was caused by two repositories offering the same application
with different version names, and causing a dependency to break when
upgrading to what was seen as the most recent version.
--
After upgrade to Ubuntu 9.10, Ap
I actually got this one wrong. Or rather, I think the n^3 answer is
wrong.
The question says "the figure" below, and while it immediately looks
like a cube, there is no way to know whether the figure is hollow. Thus,
the only correct answer would have to be the sum of small cubes visible
from the
This issue also affects me on my kodi media centre. It's not a NUC, but
rather a custom build PC with an ASUS P8H77-M motherboard and an intel
core i3-3225. Would greatly like to upgrade from 14.04 but without HDMI
sound when streaming video in a browser, that's not possible.
Had found similar wor
I can confirm that this is indeed fixed in 3.16.0-29!
$ uname -r
3.16.0-29-generic
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
[Asus P8Z77-V DELUXE] Kernel upgrade to 3.16
I am seeing this exact issue on my recently built Ubuntu 12.04 64 bit
machine: Black text on a dark gradient (as earlier posted screenshot).
Have made few changes other than installing fglrx and xfce4, using the
xfce-dusk theme (although, changing the xfce theme does not appear to
change gwibber c
Attached output from 'sudo lspci -vnvn > lspci-vnvn.log'
** Attachment added: "lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1401943/+attachment/4279688/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Public bug reported:
Under Ubuntu 14.10, I installed the latest kernel 3.16.0-28 and after
reboot my system won't boot - result is blank screen. No console from
ctrl+alt+fX.
Re-installed from 14.10 install media, choosing do-not-install-updates,
and found that strangely this still resulted in 3.1
Changed to specific kernel version package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
Kernel upgrade to 3.16.0-28 causes boot hang on my system
To manage notifications about this
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279740/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279739/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
Kernel
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279744/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279743/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279741/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
Kern
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279747/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Titl
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279750/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279746/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Just to confirm - apport collected information refers to 3.16.0-23 -
there is no issue with this kernel version. The problem is specific to
3.16.0-28. But since that version fails during boot it is not possible
to collect the apport information for the broken version.
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279745/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/140
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279748/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
Ke
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279749/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
apport information
** Tags added: apport-collected utopic
** Description changed:
Under Ubuntu 14.10, I installed the latest kernel 3.16.0-28 and after
reboot my system won't boot - result is blank screen. No console from
ctrl+alt+fX.
Re-installed from 14.10 install media, choosing do
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279742/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Title:
Kern
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1401943/+attachment/4279738/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401943
Titl
Hi Christopher, thanks for getting back to me.
I have updated the BIOS - the output from 'sudo dmidecode -s bios-version &&
sudo dmidecode -s bios-release-date' is:
2104
08/13/2013
Apart from making it hard to get into the grub menu, the BIOS upgrade
didn't seem to change much - I still end up w
I tested with the most recent 3.16 upstream kernel (3.16.7 from 201410301735),
and my system boots correctly with this kernel.
Thank you for your help!
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.16.7
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You
Christopher, I have now gone through and tested the upstream kernels
3.16.7, 3.16.4, 3.16.2, 3.16.1, and 3.16.0 - and they all work fine.
I.e. I cannot find a bad kernel in the upstream archive. It seems to
only be 3.16.0-28 that is failing on my system.
Let me know if you need me to test anything
Joseph, I have now tested with both 3.16.7-ckt1 and 3.16.7-ckt2:
3.16.7-ckt1 exhibits the same issue as 3.16.0-28 - i.e. hang at boot.
3.16.7-ckt2 does not have the issue - i.e. it appears to have been fixed
after 3.16.7-ckt1.
--
You received this bug notification because you are a member of Ub
Not sure if it adds anything - but tested this mornings update to
3.16.0-28 (3.16.0-28.38) - and the issue has not been fixed, so am back
to running 3.16.7-ckt2 on my system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
This happened to me when closing Thunar after having used the browse-
network feature to browse an external SMB share (XUbuntu 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/1233928
Title:
th
Have tonight tried with the release version of 12.10 - and the issue is
still there. See attached syslog from the latest installation attempt.
I had to use my workaround of removing my hard disk while installing
12.10 and subsequently re-attaching the hard disk. As a result I now
have 12.10 instal
Public bug reported:
Having run 12.10 beta 2 in a KVM I decided to install the latest daily
build for real only to encounter a fatal error during installation.
The install seems to run fine until suddenly reporting: Executing 'grub-
install /dev/sda' failed. This is a fatal error.
I have 2 drive
Booting off the live image for daily build 12 october does not allow me
to run apport-collect, claiming that a package is missing (or something
similar).
Experienced a hard-freeze right after the error so currently booting
live image of 12.04. Running apport-collect off the 12.04 live image
does n
12.10 beta 2 fails in the same way as the 12 October daily build of
12.10: The installer attempts to write the boot loader to the wrong
device (/dev/sda) and fails; manually changing the selection to /dev/sdb
does not produce a bootable system.
Have now re-installed 12.04, which successfully write
Attached is a tarball of /var/log/syslog, /var/log/partman, and
/var/log/installer taken at the time of the error writing boot loader to
/dev/sda.
** Attachment added: "error_logs_1.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1066325/+attachment/3398133/+files/error_logs_1.tg
Attached is a tarball with /var/log/syslog, /var/log/partman, and
/var/log/installer (same as previous attachment, but taken after
subsequently attempting to manually choose the location /dev/sdb and
/dev/sdb1 - both failing.
All logs produced with latest daily build (14th October).
** Attachment
Sorry, but the only reason I mentioned KVM was that I initially tested
in KVM with no issues what so ever - and that was what caused me to go
ahead with a direct hardware install. The issue above IS a direct
hardware install (no KVM)!
Thus, I hope this can be fixed before Thursday as I would quite
I guess a workaround will be to remove the hard disk while installing
onto the SSD then add the hard disk back in afterwards. Just a bit of a
hassle really. Surely there will be many users who have multiple drives
in their machine.
--
You received this bug notification because you are a member of
This just happened for me as well, but cannot necessarily reproduce. In
the past hour I have:
1) Created new KVM image from daily build of 12.10
2) Used software center to search for xfce
3) Used terminal to install xfce4 xfce4-goodies and xvce4-power-manager
4) Logged out and back in
5) Opened so
41 matches
Mail list logo
