This error was annoying. Something triggered it and the logs were not clear on
what.
I'm was file corruption somewhere. I had some old files in
/home/myusername/.cache/blueman*
I removed those and logged out and in. No more crash but it may not last.
--
You received this bug notification becaus
Thanks. I deliberately wasn't going to use cairo instead of libswscale
as I read it may cause performance issues for image scaling. I didn't
test it so some testing is needed to see if it matters or is even used
with guacamole.
--
You received this bug notification because you are a member of Ubu
Thanks much appreciated. I've got a development build from the freerdp-
daily PPA but it's pretty clear that the symbols still need appropriate
mapping. The Debian build has some it for the 2.1.0 build they started.
It's clearly some kind of backwards compatibility logic but I'm unclear
on intent.
FYI a Debian developer has started on freerdp 2.1.0, nothing is released as of
yet. I took a look at all the symbols in that package and was taking the wrong
approach so I didn't use my attempt.
The freerdp-daily repository guys have also kindly packaged 2.1.1.
--
You received this bug notifica
I suspect freerdp2 was derailed in politics much like the stalls and eventual
removal of a package for guacamole-server. What is currently deployed in Ubuntu
focal is a alpha development snapshot of freerdp2 2.0.0 which is buggy to the
point of being unusable for Apache guacamole and has signifi
For me initially I saw it when working with large office documents and
when attempting to do certain 1080p A/V playback. When it really got bad
I couldn't use a browser as it was happening all the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Hmm so patches were effective for:
i5-8250U Kaby Lake R i.e. Gen 8
i9-9880H and i3-8100 both Coffee Lake Gen 9
It's hard enough debugging this directly on hardware. Doing it in a VM isn't
going to be helpful.
Which CPU models are still failing with 5.3.0-52.46 or 5.3.0-52.46+lp1861395v1?
--
You
To be clear 5.3.0-51 did NOT include the backported patches.
Proposed 5.3.0-52.46 had some and 5.3.0-52.46+lp1861395v1 had more.
Out of curiosity could the people who are still having hangs on the 5.3.0-52.46
proposed or 5.3.0-52.46+lp1861395v1 kernel have different generations of CPUs?
I've got
I also had the issue on the 5.3.0-45 kernel but it happened once for 2 seconds
every two days.
It wasn't even noticeable unless you really looked for it. The 5.3 kernel
series seems to be a total write off at this point.
While it likely isn't allowed as a solution it might be less effort to
back
After it was pretty clear a stable kernel wasn't coming any time soon for 19.10
I gave up and took a dangerous leap. The only way I was going to get a 5.4
kernel was to move to 20.04.
It was dangerous and I had to get there through a do-release-upgrade -d. Highly
not recommended if you don't kno
I got about another 4 hrs before I had a 2nd hard crash with 5.3.0-52. I
once again could not shutdown or reboot and was forced to hit my reset
button. What a mess
Basically BT audio works until the connection stops. Pausing an audio
stream encourages the BT audio to unpair. The Audio sink sti
Here is the syslog content just before the hard crash on proposed 5.3.0-52 from
which I could not reboot and finally had to hit my reset button. Please note
this syslog extract contains a long string of UTF8 characters I had never seen
before in a syslog just before the crash where I had to hit
The lack of kernel stability here is really getting frustrating
With recent kernels audio playback over HDMI has stopped working for me
altogether.
I'm getting zero traction resolving it.
I get audio playback when I plug in a headset but short cables are preventing
use of that. Longer ones o
Just an FYI for those trying to figure out what the heck is going on.
The fix related to this thread wasn't in 5.3.0-51.44.
>From the changelog, which is hard to find, the fix was committed in
>5.3.0-52.46 which is currently in eoan-proposed:
5.3.0-46-generic - i915 - frequent GPU hangs / reset
I thought 5.3.0-48.41+lp1861395v1 fixed it for me. I haven't logged a hang for
a very long time.
Now out of the blue my audio stopped working altogether. I tried rebooting into
5.3.0-51.44 and I still don't have audio but I'm not hanging with that either.
--
You received this bug notification b
The test kernel 5.3.0-48.41+lp1861395v1 seems to be a major improvement!
On 5.3.0-45.37 pauses still happened rarely i.e. a single 2 second pause every
15 hrs and I hadn't noticed them until I was watching the logs for them.
5.3.0-46 and later were pausing several times a minute and the system was
I wanted the security patches in 5.3.0-46.38 so I tried updating to the
kernel from proposed i.e. 5.3.0-47.39. Sadly hangs returned within a
couple minutes of trying to use the kernel.
# cat /sys/class/drm/card0/error | head -2
GPU HANG: ecode 9:0:0x, hang on rcs0
Kernel: 5.3.0-47-generic
For what it is worth I just downgraded my kernel to 5.3.0-45.37 and I haven't
had a hang since:
https://launchpad.net/ubuntu/+source/linux/5.3.0-45.37
Not clear at all from the change log as to what brought this on in 5.3.0-46.38:
https://launchpad.net/ubuntu/+source/linux/5.3.0-46.38
--
You re
I just started having this issue on Ubuntu 19.10 w/ 5.3.0-46-generic. What a
mess...
My system is an Asrock Z370M-ITXax with an Intel i3-8100.
sudo cat /sys/class/drm/card0/error
GPU HANG: ecode 9:0:0x, hang on rcs0
Kernel: 5.3.0-46-generic x86_64
As if all my Intel NIC problems weren't
FYI in terms of sustainable options I was able to find a very hard to
find .deb with the latest driver as a DKMS module. It works fine for me
on Ubuntu 19.10. I really wish this was in a repository which was part
of universe but I'm never figured out how to do things like that.
# dpkg -l | grep e1
FYI a kernel bisection may be outside the skill set of your average user
and chances are much lower without detailed instructions. Please don't
shoot the messenger.
I too have a Asrock motherboard but a ASRock Z370M-ITX/ac. I had a lot
off trouble getting my I219-V NICs to behave on Ubuntu.
I sta
This is truly sad when a vendor that built it's business on having good
drivers has fallen so far to deprecate a perfectly good
workstation/server grade video card in my server because they won't
release updates. I really need this fixed.
--
You received this bug notification because you are a me
This same issue bit me using 18.04. I think this should really be reclassified
as an installer bug.
Ubuntu has known for many releases that a single btrfs root partition does not
work properly.
The installer should warn people when they use a single partition that is btrfs
that grub cannot writ
This shouldn't have been marked invalid. It has caused me and apparently others
grief. It wouldn't be hard to have the upgrade tool check for uncommented
cgroup lines, given they blow up an upgrade.
I'm glad my experience and work around helped someone else who ran into the
same things.
--
You
No one has any suggestions? This server 15.04 and is either already end
of life or going end of life this month. I would really like to keep it
supported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Please note the automatic captured data was on the server pre-upgrade
15.04. I did not think ubuntu-bug would run on the corrupted snapshot if
I chrooted so I didn't try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Public bug reported:
I attempted to upgrade a small home server that serves my parents from 15.04 to
15.10 to remain supported.
The first attempt at this resulted in a crash and power off in roughly the last
20% of the upgrade. The system is a desktop but it does have a good AVR capable
UPS pro
I am not convinced that the cgroup issue was the only issue here, but
since this is a single physical I can't easily go back in time to test
further.
Either way the changed summary is backwards. Once repartitioning was
completed systemd fails to boot if the /dev/cgroup fstab entry IS
present.
Th
I dug into this more on the server that failed to upgrade properly to
see if the server would work properly after switching back to systemd.
Please recall this was after a backup and restore with a much simpler
partitioning scheme. It still would not boot.
I ended up finding this line in my fstab:
faults 0 0
UUID=99649f74-7be3-427a-9eef-65a1b2922196 /mnt/tmp xfs
defaults 0 0
All a journalctl -b would gather now would be the boot log data 9 days
after this was all fixed. The log only goes back 3 days. The blkid would
capture uuids for the new partitions. Do y
nger have the logs...
Regards,
Rob
--
-"Happiness is understanding."------
Robert Hardy, B.Eng Computer Systems C.I.O. Webcon Inc.
rhardy webcon caGPG Key available (613) 276-7327
--
You received this bug notification becaus
Please note I had to upgrade to the 1.5.2 series in order to get a working
system on Ubuntu 15.04.
I have packaged this and put an upgraded package in my PPA: ppa:rhardy/webconsrp
The new package works for me. I went for a fresh config file on the new version
but that is optional.
The package is
Public bug reported:
The version of squirrelmail in universe is ancient i.e. from 2012.
Ubuntu 15.04 now ships with php 5.6 which has verify_peer on my default.
That is a good idea if you can actually configure it.
This version of squirrelmail does not support configuring your TLS
connections an
Please note attempting to mitigate this by switching back to upstart
failed as well.
Doing so did make it so the system would boot past mounting /usr however
for no obvious reason the system stopped automatically mounting the /var
partition.
With no network services running, the system would stop
Please note attempting to mitigate this by switching back to upstart
failed as well.
Doing so did make it so the system would boot past mounting /usr however
for no obvious reason the system stopped automatically mounting the /var
partition.
With no network services running, the system would stop
Public bug reported:
I recently upgraded a server from 14.10 to 15.04. The upgrade claim to
have worked but the system could not boot afterwards.
Basically when you attempt to reboot you end up at an emergency maintenance
prompt early in the boot process.
After a lot of digging one of the messag
Public bug reported:
One of my servers has a separate partition for /usr partition.
I recently tried to upgrade my server from 14.04 to 14.10 and then 15.04.
The first upgrade went well. The 2nd from 14.10 to 15.04 "succeeded" with no
obvious issues until you reboot. Unfortunately what actually
I started from a server install of 10.04 on which I added Xubuntu. Unity
must have gotten picked up along the upgrade path.
Rob
--- Original message ---
> From: Brian Murray
> To: rha...@webcon.ca
> Sent: 2013-08-27, 16:41
>
> I believe this is because you've installed unity on a Xubun
Public bug reported:
Upgrade failed from latest raring to saucy development. Success was
expected. Fortunately it was done in a sandbox so no damage occured.
"Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade:
The package 'unity' is marked for removal
My PPA has a build of pbzip2-1.15-0ubuntu1 with a few of the addons which bzip2
has. ex. bzdiff as pbzdiff etc.
If pbzip2 is an alternative it probably should be in /bin not /usr/bin. My
package made that change too.
Still missing are: bzip2recover, bzexe and bzcat. But at least it is a start.
-
This regression also affects lucid and is blocking use of kernels in
lucid updates such as linux-image-2.6.38-10-virtual.
Natty's fixed grub rebuilds fine without changes under lucid without
issue. Please fast track the fix in updates for lucid as well.
I've put the rebuild in my PPA for now. FYI
I started seeing this too around April 18th @ 11:08 on all my 10.04
Ubuntu servers.
I eventually found a static copy of my motd, which was never getting
updated in /etc/motd.tail.
I have no idea what put that there, but given it happened on all my
servers it must have been a package update and ye
I've rebuilt a deb suitable for inclusion in Universe which fixes this
bug. If anyone copied here has an idea how to actually make that happen,
please let me know.
My freeipmi_0.7.15-2ubuntu4.dsc based packages are currently in my
ppa:rhardy/webconsrp here:
https://launchpad.net/~rhardy/+archive/
Note: for dkms to work reliably you must do this:
echo 3w-sas >> /etc/initramfs-tools/modules
I'm not sure what happened but starting with 2.6.32-25-server dkms now
refuses to install the 3w-sas.ko module anywhere except
/lib/modules/2.6.32-*-server/updates/dkms/3w-sas.ko, despite my
dkms.conf exp
Here is the dkms.conf referenced in my previous comment.
** Attachment added: "dkms.conf"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607838/+attachment/1501492/+files/dkms.conf
--
3w-sas driver
https://bugs.launchpad.net/bugs/607838
You received this bug notification because you ar
The simplest way of dealing with this right now, and it is far from
painless, is to grab the 3w-sas-2.6.32.tgz src driver from 3ware/lsi and
use dkms to manage it. It took me a while to find this. The rough
process for Lucid goes:
apt-get install dkms
mkdir -p /tmp/foo; cd /tmp/foo; tar xzvpf 3w-
** Also affects: freeipmi (Debian)
Importance: Undecided
Status: New
--
broken bmc-watchdog init script/logrotate config
https://bugs.launchpad.net/bugs/594827
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Patch added: "tgz with new init script and logrotate patch"
http://launchpadlibrarian.net/50396383/freeipmi-bmc-watchdog_logrotate_init_fixes.tar.gz
--
broken bmc-watchdog init script/logrotate config
https://bugs.launchpad.net/bugs/594827
You received this bug notification because you ar
Public bug reported:
Description:Ubuntu 10.04 LTS
Release:10.04
freeipmi-bmc-watchdog:
Installed: 0.7.15-2
Candidate: 0.7.15-2
Version table:
*** 0.7.15-2 0
500 http://ca.archive.ubuntu.com/ubuntu/ lucid/universe Packages
100 /var/lib/dpkg/status
The init scrip
49 matches
Mail list logo
