With the recent Precise kernels (at least 3.2.0-[10-12] I think), the system freezes during boot with the Ubuntu logo and colored dots on screen (the dots stop progressing), when I have wistron_btns enabled in /etc/modules. I need wistron_btns on this laptop for the wireless to work, which is why I’d like to have it enabled.
This is unrelated to Bug #926007 which I also just filed: the wistron_btns freeze happens even when I’m using fbdev. (With -intel, the #926007 panic and this freeze take turns in who gets to mess with me.)
From what I’ve gathered so far, it seems that wistron_btns works fine if I manually modprobe it from my desktop, after booting without it. So that’s a workaround at least.
I can kill the freeze with Alt+PrtSc+REISUB. I’ll provide any additional info needed, though I don’t know how to produce logs when the system is frozen.
(Filing this a a separate issue as suggested by Bryce Harrington in comments of Bug #903831.)
With the -intel driver specified in xorg.conf (or without an xorg.conf so that -intel is used), booting Precise with the current 3.2.0-12 always results in a kernel panic. I’ll attach a couple of shots I took of two instances (although to me the panic looks the same in both cases).
This began within the Precise cycle: with the early kernels I was able to boot fine, although Bug #903831 did come up then.
I have yet to try 3.2.0-13 which has just been released. Once package listings pick it up I’ll give it a go and report back.
I’m able to boot by switching to fbdev in xorg.conf (the way I’m reporting this now).
Bug #904853 is related: for a i386 package installed with –force-architecture on an amd64 system, the Synaptic symptom is the same (”The list of installed files is only available for installed packages” ). The info files in /var/lib/dpkg/info don’t have a :i386 in the filename, as (I’m guessing) Synaptic figures for an :i386 package they should.
jani@saegusa:tmp$ ls /var/lib/dpkg/info/lightscribe*
/var/lib/dpkg/info/lightscribe.conffiles /var/lib/dpkg/info/lightscribe.list /var/lib/dpkg/info/lightscribe.postinst
This has been fixed in Precise (if not earlier): libsane depends on libsane-common, which now provides html/sane-mfgs.html.
jani@saegusa:~$ dlocate sane-mfgs.html
libsane-common: /usr/share/doc/libsane/html/sane-mfgs.html
jani@saegusa:~$ LC_ALL=C apt-cache depends libsane | grep libsane
libsane
Depends: libsane-common
libsane-common:i386
Suggests: libsane-extras
Replaces: libsane-extras
Replaces: libsane-extras:i386
Replaces: libsane:i386
Breaks: libsane:i386
The two dialogs are very, very inconsistent: the dialog icon they use (DIALOG_QUESTION in one, the DIALOG_ERROR in the other), the dialog window title (”Application problem” vs. none), the dialog title and explanation style (brief vs. verbose), the ignore option missing from one… It’s almost as if the engineers behind the two dialogs have intentionally tried to make them as different from one another as possible. (No offence intended, I just think it’s funny although it is a genuine accessibility problem as well.) Also, one dialog seems to be minimizable whereas the other is not — though this doesn’t appear in Blair’s screenshot; it may be something introduced in Precise which the system my screenshot is from is running.
Jason: As with Davide, it was indicator-power that was missing here. The greeter log didn’t show that though, it claimed libdatetime.so was missing even though indicator-datetime is in fact installed.
Emanuele: You’ll need to go through some hoops via the Overview page linked to on top of this report, until you get to https://launchpad.net/ubuntu/precise/+source/unity-greeter/0.2.0-0ubuntu4 where you need to pick the build for your architecture. Use dpkg –install to install the .deb file. Good luck!
After yesterday’s upgrades including libindicator7, unity-greeter crashes repeatedly until failsafe kicks in, and even then, after selecting low graphics mode for the session, it crashes. I managed to get X working again by downgrading unity-greeter back to 0.2.0-0ubuntu4 which I’m filing this report with. The crashing update was version 0.2.0-0ubuntu5.
I’m attaching the crash file.
It seems I’m not able to reproduce this on my other computer (also running up-to-date Precise), so I’ll look for differences in the setups.
Upgrade from 0.7~alpha5.1ubuntu6 to 0.7~beta2ubuntu1 brought this on: on every boot the ”Waiting for network configuration” and ”Waiting up to 60 seconds more for network” messages appear and boot is thus about 2 minutes slower than before. It also says it’s booting without network, but the network is in fact there after I log in.
Downgrading back to 0.7~alpha5.1ubuntu6 makes the wait go away again.
Reproduced this on three different computers on two different networks, both wired and wireless.
I’ve reproduced this on three separate computers, each running Precise.
Steps to reproduce:
1. Start Software Center.
2. From the File menu, choose Sync Between Computers…
3. From the registration window, choose to login to you existing account. Enter your credentials and continue forward.
What happens:
In addition to the window saying you’re now signed in, you also get the registration window. Sync is not available in the main window.
What I expect to happen:
To have only the successful sign-in window appear (i.e. not the registration window again) and have sync working in the main window.
Workaround:
Start the Sync procedure again. Repeat steps 1.-3. above. This time it works as I expect it to: the registration window doesn’t re-appear after entering my credentials, and I get the sync view in the main window.
