Everything said by TEO fully expresses my frustration with thermald.
So as not to repeat anything I'd just like to add that if I stop thermald some
other process starts it up again.
Alas, I cannot win.
$ lsb_release -a
No LSB modules are available.
Distributor ID: LinuxMint
Description:Linux
mint 18.1 (ubuntu 16.04)
i7-4810mq
vokoscreen 2.4.0 stopped displaying the area selection tool.
I am guessing 2.4.0 is an update and it is broke.
One day it worked, the next it didn't.
Purged and reinstalled. Same issue.
--
You received this bug notification because you are a member of Ubuntu
Bu
UPDATE:
Rewrote my scripts to set enp3s0 AFTER the bridge creation and deletion.
Issue with that part over.
ifdown still broken.
Unknown if script issue is related, but those scripts worked fine before the
updates.
Perhaps more than one update changed how things work.
--
You received this bug
UPDATE:
To reverify, ifdown command fails always. net-tools is broken after the update.
I have done extensive testing on my scripts adding Y/N questions to verify that
each command succeeded. They do.
Therefore, the ip and ifconfig commands do succeed inside of scripts (but not
ifdown). I was i
** Also affects: net-tools (Ubuntu)
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/1674137
Title:
ifdown unknown interface net-tools is broken
To manage n
UPDATE:
I created my own bluez 5.43 unsigned packages and installed them.
The issue is still present.
Here are the steps I took:
It was suggested that bluez 5.4 fixes the issue. However, that package
is not available for ubuntu 16.04. I was able to build my own unsigned
and upgradable package us
Same here.
Linux Mint 18.1 64bit Cinnamon Desktop (ubuntu 16.04), Bluetoothctl
v5.37.
After I wrote the below forum post I also implemented this udev change
which helped somewhat as I have an onboard bluetooth that I wanted to
disable after buying a "csr 4.0" usb dongle off of ebay. The GUI worke
Confirmed. Kernel 4.4.2 or higher fixes this nasty, nasty life ruining
raid bug. Thank God, It's gone!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320402
Title:
mdadm resyncs imsm raid in "Norma
I found this on the net after searching for "kernel 4.4 mdadm" (a page about
mdadm - follow first link):
"Kernel versions in series 4.1 through 4.4.1 have a broken RAID implementation.
Use a kernel with version at or above 4.4.2. "
I am using kernel 4.4.0-24 therefore I have broken raid.
Hope
Update results (using my fix):
Reboot with resync in progress= start where I left off (ex. 23%).
Reboot after full resync is done = go back to 0% and resync all 2TB all over
again.
Why is this bug not given importance or assigned to anyone?
It is destroying my life. That's all. I have work to do.
Small updateat the 23% sync mark I rebooted.
If my change failed then I'd go back to 0% like usual.
It didn't. I stayed at the 23% mark.
Partial confirmation the fix to /etc/init.d/sendsigs does work.
:-D
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just a note for #12. Your change to sendsigs is broken, at least for mint 18.
The process mdmon will not be found.
It is actually /sbin/mdadm --monitor
I set OMITPIDS to OMITPIDS=`pidof /sbin/mdadm`
When using pidof the full path of the executable should be specified.
Your second sed express
I have tried two different fixes for this (#12 and #13).
It won't stop.
At this point I can no longer use raid at all.
If my boot drive was raid 5 I'd be screwed as I could not turn it off at all.
I use raid 1 so I am lucky.
Can someone post a command to FORCE the raid to be clean?
Perhaps a force
I am running Linux Mint 18 64bit with Cinnamon Desktop.
I never had this issue with mint 17 (ubuntu 14.04).
Mint 18 does it every single reboot.
I have implemented the fix from #12.
I have yet to test.
It takes 4hrs for my raid 1 mirror to resync.
I cannot live with this bug.
--
You received this
This is happening to me with GDU 3.18.3.1 in linux mint 18.
A degraded raid array no longer shows up as degraded and the sync process is no
longer visible.
System:Host: xxx Kernel: 4.4.0-24-generic x86_64 (64 bit gcc: 5.3.1)
Desktop: Cinnamon 3.0.6 (Gtk 3.18.9) Distro: Linux Mi
For Peter Funk -
A chapter out of my ebook (should work for ubuntu 14.04):
Media - Burning - CDR-Tools vs CDRKit
There are two packages that can be used for burning.
They are cdr-tools and cdrkit. cdrkit is the default for Linux Mint.
Here is an article describing why some did not like cdr-tools
16 matches
Mail list logo
