[Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
First of all, thank you for your fast response! It is amazing! Yes, there was a question about secure boot, but - just as other users who experienced the same problem - I was not aware about the significant change in the handling of secure boot and the consequences thereof. Formerly Ubuntu worked with secure boot enabled, hence I saw no reason to disable it. There was some explanation about 3rd-Party-modules on that dialog, yes, but because I do not use any other sources other than those provided by Ubuntu, I didn't feel concerned. Maybe the German translation is even more misleading (however I do not recall the exact wording of the dialog on upgrade), because the section in the control panel is called "Zusätzlich Treiber" and it mentions "Proprietäre Treiber" in the text in the control panel, but not 3rd Party Software, what I think was the term used on the upgrade dialog (though I am not quite sure about that). And since everything worked when I selected the older Kernel 4.2.0-35 I did not think about this at all any longer :-( and it took quite a while to figure out the reason of the problem... If those modules get signed automatically in the future, this will help a lot... Maybe meanwhile the Dialog on Upgrade could be made a little bit more clear about the problems and that those using nvidia drivers will not be able to log in after upgrade? I uninstalled nvidia, booted with secure boot enabled and installed nvidia again (using the control panel -> "Zusätzliche Treiber" = "additional drivers"), but there was no message about secure boot there. After reboot I couldn't log in again as expected. For me it is ok now that I know the reason. But I think a lot of people might run into severe troubles... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
Thank you for this description. But it seems to be rather complicated for a normal desktop user, who has been locked out from his system after the upgrade to 16.04 (unity refuses to start without 3D-Acceleration!). Couldn't this be done automatically for modules installed as ubuntu packages? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
The problem seems to be due to uefi secure boot option now checking also the keys of modules, which the nvidia driver obviously does not provide. Disabling secure boot solved the problem for me, but completely disabling it just because there is no signature for the nvidia driver seems to be a really bad option! Shouldn't there be an option to install signatures for third party drivers, that are supported (nvidia, virtualbox etc)? I think this bug rather affects the package 'shim'... ** Also affects: shim Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1574732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574732] Re: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable
I just upgraded to 16.04 and can't log in any longer with the latest (default) kernel 4.4.0-21. If i select an older kernel (4.2.0-35) everything works fine. Trying to load nvidia drivers manually say something like 'required key missing' (i would have to reboot with the latest kernel to see the exact wording however). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574732 Title: Regression: Kernel Update in 16.04 from last days renders nvidia driver unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242057] [NEW] package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: This happend during a dist-upgrade to 13.10. A lot of error messages were displayed, including a message, that the upgrade process will terminate and leave the system in an inconsistant state. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: tex-common 4.04 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 14:57:51 2013 DuplicateSignature: package:tex-common:4.04:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 MarkForUpload: True PackageArchitecture: all SourcePackage: tex-common Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242057 Title: package tex-common 4.04 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1242057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174429] Re: error: unknown type name ”u_int8_t” when building
Hallo, probably i am totally wrong here, but i had some unexpected behaviour when installing these packages from proposed. Background: i am suffering from Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169984, ie. there was no hdmi output available. For this reason i installed the new proposed kernel in proposed, that should fix it. I also installed the proposed alsa-packages, as i was not sure, whether they would be necessary too. HDMI worked then as expected, but after some time - always listening to internet radio - the x-window-system froze: The mouse did no longer respond nor most of the keyboard commands. The internet radio however continued playing. The only things i could do in this state were: - terminate the X-Server using Ctrl-Alt-Backspace and then logging in again. - switching to console and back (logging into my user account in the text console even brought the internet radio back!) This happened to me several times. Today i reinstalled the "old" packages manually and it did not happen again (for now). There was absolutely nothing relevant in syslog, kern.log and Xorg.0.log. Hope, it's not too confusing... Once again, probably the failures were just a coincidence and not really related to those updates. But how can we know? Maybe the combination of HDMI-Output with the newest proposed kernel and these new alsa-lib's should be tested by other users? I listened to internet radio (http://gffstream.ic.llnwd.net/stream/gffstream_w13b) using vlc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174429 Title: error: unknown type name ”u_int8_t” when building To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1174429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 515386] Re: No attachment when Thunderbird is set as default client.
Hi,
i have the same problem with raring.
for me there seem to be at least 2 errors in the script:
in open_gnome the wrong variable is used to find the desktop file (browser
instead of desktop)
and in desktop_file_to_binary() the grep command finds multiple occurences of
'Exec'. The supposed patch below only takes the first one and removes all
following lines.
hence i suppose the following changes, that seem to work for me:
@@ -319,11 +319,11 @@
unset IFS
[ "$dir" -a -d "$dir/applications" ] || continue
file="$dir/applications/$desktop"
[ -r "$file" ] || continue
# Remove any arguments (%F, %f, %U, %u, etc.).
-command="`grep -E "^Exec(\[[^]=]*])?=" "$file" | cut -d= -f 2- | sed
-e 's/ .*$//'`"
+command="`grep -E "^Exec(\[[^]=]*])?=" "$file" | cut -s -d= -f 2- |
sed -e 's/ .*$//;2,$d'`"
command="`which "$command"`"
readlink -f "$command"
return
done
}
@@ -510,11 +510,11 @@
open_gnome()
{
local client
local desktop
desktop=`xdg-mime query default "x-scheme-handler/mailto"`
-client=`desktop_file_to_binary "$browser"`
+client=`desktop_file_to_binary "$desktop"`
echo $client | grep thunderbird > /dev/null 2>&1
if [ $? -eq 0 ] ; then
run_thunderbird "$client" "$1"
fi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/515386
Title:
No attachment when Thunderbird is set as default client.
To manage notifications about this bug go to:
https://bugs.launchpad.net/simple-scan/+bug/515386/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169984] Re: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV
I also confirm the proposed kernel fixed audio via DisplayPort for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169984 Title: 3.8.0-18 HDMI audio regression: Either oops or opening device fails with -ENODEV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1169984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164196] Re: system crash while watching tv streams. Syslog message about snd_pcm_avail()
the bug seems to be independent of the other bug (gpu hangs). i activated sna acceleration as pointed out in comment #75 of the other bug, but the system crash happened again (while listening to internet radio) without any gpu-hang in the logs. After hard reset i found this in syslog: pulseaudio[2739]: [alsa-sink] alsa-util.c: snd_pcm_avail() gab einen Wert zurück, der außerordentlich groß ist: 3487192 Byte (19768 ms). pulseaudio[2739]: [alsa-sink] alsa-util.c: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber »snd_hda_intel«. Bitte melden Sie dieses Problem den ALSA-Entwicklern. pulseaudio[2739]: [alsa-sink] alsa-util.c: snd_pcm_dump(): -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164196 Title: system crash while watching tv streams. Syslog message about snd_pcm_avail() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164196] Re: system crash while watching tv streams. Syslog message about snd_pcm_avail()
additional information: i also suffer from this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157649 maybe these crashes were a sideeffect of the other bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1164196 Title: system crash while watching tv streams. Syslog message about snd_pcm_avail() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1164196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1164196] [NEW] system crash while watching tv streams. Syslog message about snd_pcm_avail()
Public bug reported: while watching tv streams in vlc the system hangs. occured several times, with kernel 3.5.0-23-generic as well as with current 3.5.0-26-generic. ubuntu 12.10 pulseaudio: Installiert: 1:2.1-0ubuntu4 Kandidat:1:2.1-0ubuntu4 Versionstabelle: *** 1:2.1-0ubuntu4 0 500 http://ftp.stw-bonn.de/ubuntu/ quantal/main amd64 Packages 100 /var/lib/dpkg/status syslog says: pulseaudio[2652]: [alsa-sink] alsa-util.c: snd_pcm_avail() gab einen Wert zurück, der außerordentlich groß ist: 605184 Byte (3152 ms). pulseaudio[2652]: [alsa-sink] alsa-util.c: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber »snd_hda_intel«. Bitte melden Sie dieses Problem den ALSA-Entwicklern. pulseaudio[2652]: [alsa-sink] alsa-util.c: snd_pcm_dump(): pulseaudio[2652]: [alsa-sink] alsa-util.c: Hooks PCM pulseaudio[2652]: [alsa-sink] alsa-util.c: Its setup is: pulseaudio[2652]: [alsa-sink] alsa-util.c: stream : PLAYBACK pulseaudio[2652]: [alsa-sink] alsa-util.c: access : MMAP_INTERLEAVED pulseaudio[2652]: [alsa-sink] alsa-util.c: format : S16_LE pulseaudio[2652]: [alsa-sink] alsa-util.c: subformat: STD pulseaudio[2652]: [alsa-sink] alsa-util.c: channels : 2 pulseaudio[2652]: [alsa-sink] alsa-util.c: rate : 48000 pulseaudio[2652]: [alsa-sink] alsa-util.c: exact rate : 48000 (48000/1) pulseaudio[2652]: [alsa-sink] alsa-util.c: msbits : 16 pulseaudio[2652]: [alsa-sink] alsa-util.c: buffer_size : 16384 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_size : 8192 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_time : 170666 pulseaudio[2652]: [alsa-sink] alsa-util.c: tstamp_mode : ENABLE pulseaudio[2652]: [alsa-sink] alsa-util.c: period_step : 1 pulseaudio[2652]: [alsa-sink] alsa-util.c: avail_min: 15617 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_event : 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: start_threshold : -1 pulseaudio[2652]: [alsa-sink] alsa-util.c: stop_threshold : 4611686018427387904 pulseaudio[2652]: [alsa-sink] alsa-util.c: silence_threshold: 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: silence_size : 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: boundary : 4611686018427387904 pulseaudio[2652]: [alsa-sink] alsa-util.c: Slave: Hardware PCM card 0 'HDA Intel PCH' device 3 subdevice 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: Its setup is: pulseaudio[2652]: [alsa-sink] alsa-util.c: stream : PLAYBACK pulseaudio[2652]: [alsa-sink] alsa-util.c: access : MMAP_INTERLEAVED pulseaudio[2652]: [alsa-sink] alsa-util.c: format : S16_LE pulseaudio[2652]: [alsa-sink] alsa-util.c: subformat: STD pulseaudio[2652]: [alsa-sink] alsa-util.c: channels : 2 pulseaudio[2652]: [alsa-sink] alsa-util.c: rate : 48000 pulseaudio[2652]: [alsa-sink] alsa-util.c: exact rate : 48000 (48000/1) pulseaudio[2652]: [alsa-sink] alsa-util.c: msbits : 16 pulseaudio[2652]: [alsa-sink] alsa-util.c: buffer_size : 16384 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_size : 8192 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_time : 170666 pulseaudio[2652]: [alsa-sink] alsa-util.c: tstamp_mode : ENABLE pulseaudio[2652]: [alsa-sink] alsa-util.c: period_step : 1 pulseaudio[2652]: [alsa-sink] alsa-util.c: avail_min: 15617 pulseaudio[2652]: [alsa-sink] alsa-util.c: period_event : 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: start_threshold : -1 pulseaudio[2652]: [alsa-sink] alsa-util.c: stop_threshold : 4611686018427387904 pulseaudio[2652]: [alsa-sink] alsa-util.c: silence_threshold: 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: silence_size : 0 pulseaudio[2652]: [alsa-sink] alsa-util.c: boundary : 4611686018427387904 pulseaudio[2652]: [alsa-sink] alsa-util.c: appl_ptr : 101161136 pulseaudio[2652]: [alsa-sink] alsa-util.c: hw_ptr : 101296048 pulseaudio[2652]: [alsa-sink] alsa-util.c: snd_pcm_delay() gab einen Wert zurück, der außerordentlich groß ist: -1691232 Byte (-8808 ms). pulseaudio[2652]: [alsa-sink] alsa-util.c: Dies ist höchstwahrscheinlich ein Fehler im ALSA-Treiber »snd_hda_intel«. Bitte melden Sie dieses Problem den ALSA-Entwicklern. pulseaudio[2652]: [alsa-sink] alsa-util.c: snd_pcm_dump(): pulseaudio[2652]: [alsa-sink] alsa-util.c: Hooks PCM pulseaudio[2652]: [alsa-sink] alsa-util.c: Its setup is: pulseaudio[2652]: [alsa-sink] alsa-util.c: stream : PLAYBACK pulseaudio[2652]: [alsa-sink] alsa-util.c: access : MMAP_INTERLEAVED pulseaudio[2652]: [alsa-sink] alsa-util.c: format : S16_LE pulseaudio[2652]: [alsa-sink] alsa-util.c: subformat: STD pulseaudio[2652]: [alsa-sink] alsa-util.c: channels : 2 pulseaudio[2652]: [alsa-sink] alsa-util.c: rate : 48000 pulseaudio[2652]: [alsa-sink] alsa-util.c: exact rate : 48000 (48000/1) pulseaudio[2652]: [alsa-sink] alsa-util.c: msbits : 16 pulseaudio[2652]: [alsa-sink] alsa-util.c: buffer_size :
