Isn't this against os-prober? It was on openSUSE.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772314
Title:
Ubuntu UEFI grub does not add Arch Linux correctly
To manage notifications about this
This is easily verifiable. Have Arch Linux installed and add any Ubuntu
version to your system. Take a look at the /etc/boot/grub.cfg file. You
will see that /initramfs-linux.img is missing and also you will not be
able to boot into Arch. The only way to boot Arch is via the fallback
kernel.
--
Y
Public bug reported:
If you have a UEFI system with Arch Linux installed, then add a Ubuntu system
in Multi-boot the initrd line is wrong for Arch Linux.
Ubuntu 30_os-prober adds "initrd /intel-ucode.img" and Arch fails to boot.
Arch requires that line to be "initrd /intel-ucode.img /initramfs-li
I have a new PC SSD using UEFI/GPT and I am experiencing none of these problems
booting Windows 10.
I installed Windows 10, then Xubuntu 16.04, Xubuntu 18.04 and today Xubuntu
18.10 with zero problems.
Boot entry for Windows 10 default:
menuentry 'Windows Boot Manager (on /dev/sdc1)' --class wind
** Information type changed from Private 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/1723954
Title:
blueman-applet crashed with AttributeError in setup_icon_path():
'NoneType' object h
I can confirm that I've been seeing this the past couple of days too:
W:
gpgv:/var/lib/apt/lists/ppa.launchpad.net_noobslab_themes_ubuntu_dists_xenial_InRelease:
The repository is insufficiently signed by key
4FA44A478284A18C1BA4A9CAD530E028F59EAE4D (weak digest)
W:
gpgv:/var/lib/apt/lists/ppa.
This is working as it should work now. Is there any timeline on when it will be
put out to the masses?
I install a kernel and before rebooting I purge the 3rd kernel back like I've
always done.
If you autoremove the kernel it leaves the residual config files, which have to
purged with a command
Today when updating via cli 4.4.0-2-generic kernel was waiting to be
autoremoved. So after getting the updates I autoremoved that kernel.
This left me with 2 kernels 4.4.0-4-generic and 4.4.0-6-generic which is
precisely how it is supposed to work.
I think this is working great now.
--
You recei
I let 3 kernels remain on my Xubuntu 16.04 pc: 4.3.0-7-generic, 4.4.0-2-generic
and 4.4.0-4-generic. Just to see what would happen.
Today when 4.4.0-6-generic kernel came through in regular updates and
when it installed and I rebooted.
I again checked for updates via cli and it wanted to autor
I could not successfully run the command.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1458204
Title:
removing kernels should not require a restart afterward
To manage notifications about this bug
The installation of the 4.4.0-2-generic in Xenial 16.04 went well, It
left 3 kernels in 01autoremove-kernels so I manually purged the 3rd
oldest one. Now there are 2 there. I updated my /etc/kernel/postinst.d
/apt-auto-removal with version 5 above.
--
You received this bug notification because yo
Manually purged the 4.3.0-5-generic kernel and that left the
4.3.0-6-generic and 4.3.0-7-generic kernels in the 01autoremove-kernels
file. Which is great.
My only question is why does it require a reboot when the 3rd oldest
kernel is deleted? I don't think this should be happening either.
--
You
Got the 4.3.0-7-generic kernel on Xubuntu 16.04 in today's updates and the
01autoremove-kernels file
contains the last 3 kernels, which I'm fine with. I'll purge the 3rd oldest
one. I prefer purging them
manually instead of using autoremove because autoremove leaves the "Residual
Config" files
Then I performed a sudo apt autoremove and the 4.3.0-2-generic was removed.
The 01autoremove-kernels did not change and still contains the last 2 kernels,
which is good.
The output is attached.
It gave an erroneous error about the kernel header for 4.3.0-2-generic
not being found but since it was
Jarno, I did notice that those commands were in the original script after I
posted that.
I got the 4.3.0-6-generic installed in Xubuntu 16.04 just a while ago and your
script worked flawlessly.
I had 3 kernels: 4.3.0-2-generic, 4.3.0-5-generic and 4.3.0-6-generic after
installation and the 01aut
I got the same and sudo dpkg -P libxapian-1.3-4 1.3.3-0ubuntu2 didn't work.
I had to manually install libxapian-1.3-5. Then it worked.
cavsfan@cavsfan-le-beast:~$ sudo dpkg -P libxapian-1.3-4 1.3.3-0ubuntu2
(Reading database ... 250782 files and directories currently installed.)
Rem
Thanks for the attention to this issue that effects every debian version
including Mint back to Trusty 14.04.
I copied your version 4 script into my /etc/kernel/postinst.d/apt-auto-removal.
I will post the entire output resulting from the next kernel that gets added.
I have a 64 bit version of Xub
Jarnos, I have always had a text file with the kernels listed on it and when I
have 3 I delete the 3rd one leaving me 2.
This has been good since 2009. Since it wasn't asking me to autoremove anything
I just entered:
sudo apt-get purge linux-headers-4.3.0-1 linux-headers-4.3.0-1-generic
linux-im
Jarnos, I can confirm that your /etc/kernel/postinst.d/apt-auto-removal and
adding the cron job resolves this problem.
I installed the 4.3.0-5-generic kernel and rebooted and then manually purged
the 4.3.0-1-generic and it gave some erroneous errors about not being able to
find the DKMS modules
Thanks! I did that.
We'll see when the next kernel comes through in updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all
I run an alias to do my updating and it's this:
sudo apt-get update && sudo apt-get upgrade && sudo apt-get autoclean
When the update happens and there is a kernel waiting to be dist-upgraded I
believe the
/etc/apt/apt.conf.d/01autoremovekernels file has been manipulated to include
parts of the
I've been getting this error about libjpeg-progs for a while now.
I removed the package and left libjpeg-turbo-progs installled. It also took
xscreensaver-data-extra with it when purged.
I re-installed libjpeg-turbo-progs and xscreensaver-data-extra.
setup an alias so the other updates would comp
In Xubuntu 16.04 I get this:
~$ fusion-icon
* Detected Session: xubuntu
* Searching for installed applications...
Segmentation fault (core dumped)
I have not been able to use the fusion-icon for quite some time in any
Ubuntu version.
--
You received this bug notification because you are a memb
I just got this in Wily Xubuntu 15.10 while trying to add a song just
after installation of Audacious.
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959981
Title:
audacious cras
I also found a work around: once the new kernel is installed and it's
wanting to reboot, delete the 3rd oldest kernel or autoremove it before
rebooting and then the /etc/apt/apt.conf.d/01autoremovekernels file will
contain the 3 kernels, which is better than having one.
--
You received this bug n
*** This bug is a duplicate of bug 1051935 ***
https://bugs.launchpad.net/bugs/1051935
Had this twice on Xubuntu 15.10 without doing anything.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/869704
*** This bug is a duplicate of bug 1051935 ***
https://bugs.launchpad.net/bugs/1051935
If the fix was released for bug #1051935 this is definitely not a
duplicate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
This just happened to me on Xubuntu 15.10 when 4.2.0-11-generic was installed.
It wanted to leave me with one kernel.
You can refer to these two posts for the detail:
http://ubuntuforums.org/showthread.php?t=2251168&page=4&p=13361806#post13361806
http://ubuntuforums.org/showthread.php?t=2251168&
I wouldn't know. I rearranged my partitions and did a fresh install of
Xubuntu 15.10.
On 09/18/2015 04:12 AM, Martin Wimpress wrote:
> Does this issue still happen in 15.10?
>
> -- You received this bug notification because you are subscribed to
> the bug report. https://bugs.launchpad.net/bugs/
I just got this exact same error when trying to click on the Fusion
Icon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1290993
Title:
fusion-icon crashed with SIGSEGV in ccsObjectGetInterface_()
T
Public bug reported:
Got this upon booting into the system.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libxfce4panel-2.0-4 4.12.0-3ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Dat
*** This bug is a duplicate of bug 1495494 ***
https://bugs.launchpad.net/bugs/1495494
Public bug reported:
Got this upon booting into the system.
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: libxfce4panel-2.0-4 4.12.0-3ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.
I have no idea. I am testing Ubuntu Mate 15.10 with that partition.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434155
Title:
Pluma Ubuntu Mate Skipped: missing required field "Disassembly"
To m
** Tags added: utopic wily
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
except the latest one
To manage notific
How can you run that when
'''
/etc/kernel/postinst.d/apt-auto-removal
'''
is automagically run at the end of
'''
entering sudo apt-get purge <4 kernel modules>.
...
let alone when auto-remove is run.
'''
you will never get the chance.
--
You received this bug notification because you are a m
This continues on even in Linux Mint as well as Ubuntu.
I don't think /etc/kernel/postinst.d/apt-auto-removal should be triggered when
you delete a kernel no matter if it's the17th, 3rd, or 2nd to last kernel.
It is triggered when you just manually delete kernels:
sudo apt-get purge linux-headers
What how to?
On 05/12/2015 01:47 PM, eric tennant wrote:
> Hi, can you please advise me on the how to.
> Would appreciate it.
> Regards
> Eric Tennant
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Since this happens on every version from 14.04 to 15.10 is the problem
that it think my PC is a phone? There should be a way to distinguish
whether the system is a phone or a pc/laptop. Maybe phones should keep
one kernel but I believe PC/laptops should be able to retain 2 kernels.
The /etc/kernel/
The solution in Wiley was to set
gsettings set org.gnome.settings-daemon.plugins.xsettings overrides
to {"Gtk/ShellShowsAppMenu":<0>}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298666
Title:
Pre
I have installed wiley and in a gnome flashback (with compiz) session there is
no option for preferences under the edit tab.
Therefore there is no option to not wrap lines, show line numbers, etc.
** Tags added: wiley
--
You received this bug notification because you are a member of Ubuntu
Bugs
This just happened on Trusty 14.04.2 LTS when 3.13.0-52-generic was
installed on my computer.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440608
Title:
/etc/kernel/postinst
I agree it is dangerous to auto remove all old kernels but that is exactly what
I am experiencing on Vivid.
I opened this bug because of that reason
/etc/kernel/postinst.d/apt-auto-removal is broken and only keeps the latest
kernel.
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608
Perh
I agree you should not have too many kernels on your system but, you
should always have 2 regardless. One for backup and one to use. I would
expect autoremove to remove the 3rd oldest kernel but not the only other
kernel on the system. Which is the case as the last 2 kernel installs
did the exact s
Please mark the bug as affecting you then.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440608
Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
except the latest one
T
This has been happening on 3 different Vivid installs and 2 different
flavors vanilla Ubuntu and Ubuntu Mate. It happens every time a new
kernel is added without fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Attachment added: "the contents of /etc/apt/apt.conf.d/01autoremove-kernels
after the 3rd oldest kernel is removed."
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4367067/+files/after%20autoremoval%20of%203%20oldest%20kernel
--
You received this bug notification b
After rebooting and autoremoving the 2nd oldest kernel the
/etc/apt/apt.conf.d/01autoremove-kernels file reverts to listing the
3.19.0-11-generic and 3.19.0-12-generic kernels. So only one kernel, the
latest 3.19.0-12-generic is left.
--
You received this bug notification because you are a member
The workaround to keep the latest two kernels is to edit the
/etc/apt/apt.conf.d/01autoremove-kernels file and change it to list the
latest 2 kernels.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440
Public bug reported:
After installing a 3rd kernel currently 3.19.0-12-generic, the
/etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed to
be autoremoved. But once autoremove is completed the machine requests
I got this errror at boot this morning.
** Attachment added: "My /etc/cups/cups-browsed.conf file"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1431041/+attachment/4356970/+files/cups-browsed.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Information type changed from Private 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/1434155
Title:
Pluma Ubuntu Mate Skipped: missing required field "Disassembly"
To manage notificatio
*** This bug is a duplicate of bug 1432138 ***
https://bugs.launchpad.net/bugs/1432138
I get this error daily. This time I awoke it from suspend and got the crqash
report.
This is on Ubuntu Mate Vivid 15.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Keep getting this same error over and over again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1103456
Title:
oneconf-query crashed with dbus.exceptions.DBusException in
call_blocking(): org.free
Just got this error on a brand new install of Vivid Mate but got this:
oneconf-query crashed with dbus.exceptions.DBusException in call_blocking():
org.freedesktop.DBus.Error.ServiceUnknown: The name :1.82 was not provided by
any .service files
--
You received this bug notification because you
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cavsfan1329 F pulseaudio
Date: Wed Mar 11 08:22:26 2015
ExecutablePath: /usr/src/linux-headers-3.19.0-8-generic/scripts/basic/fixdep
Adding version log (/proc/version_signature).
** Attachment added: "version.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1430780/+attachment/4341132/+files/version.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Public bug reported:
Received this error while getting updates.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: nvidia-settings 346.35-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.16.2-0u
I just got this at bootup in VIvid.
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356823
Title:
aptd crashed with AttributeError in
_remove_from_connection_no_raise(): 'None
I just got this again on Vivid 15.04 when 3.18.0-9-generic kernel installed.
Going to try the fix from post #100. I did it on Trusty now on Vivid.
Then the next kernel install will tell if it worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Those other workarounds are mentioning re-installing the driver. That
may prevent the error but during the next kernel installation you will
likely see the error again. Post #100 by dino99 is a modification that
you make for future kernels so they do not get the error. The error
message to me is bo
Refer to post #100 for the fix by dino99.
If you simply reinstall the driver it will happen the next time a kernel is in
updates.
I believe dino99's fix should fix it once and for all.
I'm waiting on the next kernel to come along to verify that.
--
You received this bug notification because you
Refer to post #111 for how to unsubscribe. Neolaser mentioned it once
there already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268257
Title:
nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updat
Got a new kernel in Trusty 14.04 yesterday and got this error. Did the
steps in post #100 that dino99 suggested. Looked good rebooted and all
is fine. Will see if that fixes the problem from now on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I tried to install systemd-sysv which wanted to uninstall upstart and
nvidia-prime and got this.
Nvidia-prime could not be removed due to dependency issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I installed Vivid Alpha 1 from ISO yesterday and when I installed the 331.113
drivers I did not get this error at all.
Everything was normal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1268257
Tit
Public bug reported:
Got the checksum error when DKMS modules were being built for nvidia
driver 331.113 when kernel 3.16.0-28-generic was added.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.113-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Una
nvidia-331 331.113-0ubuntu2 as well as all of the previously mentioned
components just upgraded and no errors occurred so this bug may be moot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401251
Ti
This might matter: I just checked for updates and libcuda1-331,
nvidia-331, nvidia-331-uvm, nvidia-opencl-icd-331, are now being
installed after the error. I thought nvidia-331 updates once just before
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Public bug reported:
I have no further information.
Still getting the same error during dkms updates for 331.113-0ubuntu1, which
was installed today.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.113-0ubuntu1
Uname: Linux 3.18.0-031800-lowlatency x86_64
NonfreeKernelM
Installed the 3,18 kernel from http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.18-vivid/ not sure if that matters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401251
Title:
nvidia-331 331.113-0
have bugs. Who is apport them?
> 30 Kas 2014 23:30 tarihinde "Cavsfan" <1268...@bugs.launchpad.net> yazdı:
>
>> I agree that this error is not really an error and does not affect the
>> DKMS modules at all.
>> I get the error when a new kernel is installed but th
I agree that this error is not really an error and does not affect the DKMS
modules at all.
I get the error when a new kernel is installed but the nvidia-331 and
nvidia-331-uvm DKMS modules are successfully built.
This can be seen when the kernel is subsequently removed and the DKMS modules
are
Conky-all is available in the Vivid repositories.
cavsfan@cavsfan-MS-7529:~$ apt-cache policy conky-all
conky-all:
Installed: 1.9.0-6
Candidate: 1.9.0-6
Version table:
*** 1.9.0-6 0
500 http://us.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg
conky-std does not provide all of the same features as conky-all. Conky-
all is really necessary to run many conkys.
** Changed in: conky-all (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Public bug reported:
Exactly like bug #1298016 but 331.89 instead of 331.88.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: nvidia-331 331.89-0ubuntu6
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersi
*** This bug is a duplicate of bug 1377258 ***
https://bugs.launchpad.net/bugs/1377258
I booted into Vivid with systemd and the time is ahead by 5 hours exactly.
I thought it was fixed with yesterday's update but I guess not.
cavsfan@cavsfan-MS-7529:~$ apt-cache policy systemd
sy
I booted into vivid with systemd and the time was 4 hours behind US EST.
I just thought I'd mention it. I see a fix is coming.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377258
Title:
/e
ooted Utopic with systemd and got the attached message. The time
was right but has gotten that same message at boot and the time was
still off before too. The time has been correct for the past few days.
"cavsfan@cavsfan-MS-7529:~$ systemctl status hwclock
hwclock.service
Loaded: masked
I just got this again with Utopic Mate Remix and I have 331.89 Nvidia
drivers installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364630
Title:
init: Error while reading from descriptor: Broke
This bug is not a duplicate of
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377698
That involved just upstart boot, this bug just involves systemd boot.
And it's still broken here as of today. Only sudo ntpdate ntp.ubuntu.com will
fix the time.
** This bug is no longer a duplicate
This is still broken on my system I boot and I see a message systemd-
fcsk detects that the system time is 4 hours behind due probably to a
hardware bios setting and it says it corrected it but when it comes up
it is still 4 hours behind.
--
You received this bug notification because you are a me
I booted using systemd with Gnome Flashback (with Compiz).
Today I got the same 4 hours behind US ET.
I had to enter sudo ntpdate ntp.ubuntu.com to correct the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I just got this error when kernel 3.16.0-23-generic was installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370859
Title:
Error! Bad return status for module build on kernel: 3.16.0-16-generic
I also have Utopic Mate Remix installed and it was also happening to
this system when booting with systemd too but that seems to be
intermittent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1382208
Public bug reported:
This bug is identical to
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377698
except it only happens when booting with systemd.
Even with UTC=no, Ubuntu stores the time as UTC at shutdown. But since UTC=no,
it expects the time as local, thus applies no timezon
I got this error but I'm also getting an error about nvidia-prime not
installing correctly.
The following packages will be upgraded:
nvidia-prime
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/11.4 kB of archives.
After this opera
As a temporary workaround:
gksudo gedit /etc/cron.daily/ntpdate
Add this and save it:
#!/bin/sh
ntpdate ntp.ubuntu.com
Then sudo chmod 755 /etc/cron.daily/ntpdate to make it executable.
I found that on this page:
https://help.ubuntu.com/community/UbuntuTime
When it boots up the time is fou
this does not fix it:
cavsfan@cavsfan-MS-7529:~$ sudo dpkg-reconfigure tzdata
Current default time zone: 'America/New_York'
Local time is now: Tue Sep 30 08:09:32 EDT 2014.
Universal Time is now: Tue Sep 30 12:09:32 UTC 2014.
The only thing that will fix it is sudo ntpdate ntp.ubunt
Same thing on Utopic Unicorn 14.10 after installing 3.16.0-18-generic
kernel and rebooting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374460
Title:
nvidia-331 331.89-0ubuntu5: nvidia-331 kernel
I just got this exact error after installing 3.16.0-18-generic kernel and
rebooting.
This is on Utopic Unicorn 14.10 Mate Remix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374460
Title:
nvidia-
I got this exact error when I removed kernel 3.16.0-14-generic as I had 3
kernels installed.
Although when that kernel was removed and when it was installed it gave an
error like it didn't properly install the nvidia driver but this is what was in
the output indicating that the driver was indeed
Attachment text file for the above.
** Attachment added: "DKMS removed the nvidia modules from 3.16.0-14-generic
although there was an error when it was installed"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1373498/+attachment/4213817/+files/DKMS%20removed%20th
I received this "nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm kernel module
failed to build".
Same error only with nvidia-331-uvm instead of nvidia-331.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
I received this same error after rebooting when kernel 3.16.0-16-generic
was installed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370890
Title:
nvidia-331-uvm 331.89-0ubuntu5: nvidia-331-uvm ke
** Tags added: systemd-boot utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922129
Title:
notify-osd crashed with signal 5 in _XReply()
To manage notifications about this bug go to:
https://bu
I got this again today on Utopic when 3.16.0-14-generic was installed.
Although when I deleted the 3.16.0-12-generic kernel the
/lib/modules/3.16.0-12-generic/updates/dkms/nvidia_331.ko was deleted so it was
installed even though it had gotten the error when it was installed.
--
You received th
Same thing on Utopic Mate:
nvidia-331 331.89-0ubuntu3: nvidia-331 kernel module failed to build.
See my previous comment for the exact same details Mate gave.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
r/lib/dkms/nvidia-331/331.89/build/make.log does not exist.
I have the following nvidia files installed and it does 2 DKMS updates to the
kernel and the 2nd one does not get this error.
cavsfan@cavsfan-MS-7529:~$ dpkg -l | grep nvidia
ii nvidia-3313
exist.
It performed 2 DKMS processes and the 2nd one didn't get the error just the
first one.
This is what is installed:
cavsfan@cavsfan-MS-7529:~$ dpkg -l | grep nvidia
ii nvidia-331331.89-0ubuntu2
amd64NVIDIA b
Public bug reported:
Utopic does not currently have a way to get conky-all through the repositories.
Could it be added as it is highly requested by many people?
** Affects: conky-all (Ubuntu)
Importance: Undecided
Status: New
** Tags: conky-all utopic
--
You received this bug no
1 - 100 of 215 matches
Mail list logo
