Dear Marco, Can you help me understand from which point in time you'd
like to get the trace? Gnome does not typically crash for me, I got a
crash only once. My problem is more the garbled display configuration,
that makes high resolution modes unusable for me. Do you mean I should
try to provoke mo
> are you sure these lines come from rsyslog and not the systemd
journal?
I'm so sorry, but I think I'm not making myself clear. I'm not sure
about anything here. I reported this issue _because_ I'm not sure.
Quoting from myself: I'm not nearly knowledgeable enough to understand
the components inv
I have deleted ~/.config/monitors.xml, then rebooted and logged in
again.
The file is not recreated automatically, it seems? The new default
display configuration for Gnome is now already 4K@60 Hz. I have waited
once, until the displays go into suspend, then resumed, and the problem
appeared immed
You say that future versions of logcheck will unsplit long lines? That
sounds great! But, my (naiive) question for this issue is, why do we
even suddenly have to unsplit any lines? This was never happening with
Ubuntu 22.04, so what changed? And should it not be possible to
configure line splitting
Thanks @rpil2 for the reply! However, I'm not so much concerned about
the content of the messages. My challenge is, that the messages are
broken into multiple lines. That makes it harder to usefully apply tools
like logcheck.
For the life of me, I could not find how I can configure the line
breaki
Public bug reported:
I have been using logcheck for automatic even emails since at least
Ubuntu 18.04 successfully. Recently I upgraded from Ubuntu 22.04 to
Ubuntu 24.04, and ever since, I have a problem with long kernel
messages. The message appears to be split into multiple lines in
/var/log/sys
Do you need anything else from me, or is this enough to continue the
investigation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
Title:
[nvidia] On high resolution modes, after screen resum
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821790/+files/monitors.xml.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Attachment added: "modified.conffile..etc.init.d.apport.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821789/+files/modified.conffile..etc.init.d.apport.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821788/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821786/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821787/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081199
apport information
** Tags added: apport-collected
** Description changed:
This is a follow-up issue from
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2075525, and some of the information from the earlier issue
may apply here.
I have configured the host scre
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/2081199/+attachment/5821785/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
This is a follow-up issue from
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2075525, and some of the information from the earlier issue
may apply here.
I have configured the host screen with two monitors extending the desktop.
They are both configured
For anyone coming here, the follow-up issue is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/2081199
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2075525
Title:
After scr
I'm sorry for coming back to this, but the new display cable does *not*
help.
I have just had actually my worst Gnome crash so far, and it happened
immediately on the first try, after upgrading my HDMI cable to a
supposedly decent 2.1 standards cable, and switching again to 4K
resolution at 60 Hz
Ok, so, for what its worth, here is my current summary:
- I already have `ubuntu-drivers-common` `1:0.9.7.6ubuntu3.1` installed since
a few days, and it did not help resolve the problem.
- I have reduced the monitor resolution, and this reliably circumvents the
problem (no more issues since 24h
Also, the issue goes away when I turn down the resolution to 1920x1080
again. So it is certainly tied to the high resolution.
The problem may have something to do with the HDMI cable on one of the
two monitors. Only one monitor uses HDMI, the second monitor uses
DisplayPort. Before I switched to H
Dear @vanvugt and all,
I am so happy to find this issue, because I suffer from the same problem.
However I am very surprised to see this issue closed as fixed, when @raffaeler
was saying that the proposed fix does *not* solve the main problem (and it does
not solve it for me either)!
So the ori
Still the same for default clusterssh installation 4.13 on Ubuntu 18.04.
Copy-pasting lines with backslash (\) or pipe (|) inserts them as
backtick (`) for me. This breaks a really useful tool, any help greatly
appreciated.
--
You received this bug notification because you are a member of Ubuntu
Is it known if 18.04 has the patches active to support ryzen out of the
box? I have upgraded to 18.04 recently and the system has just hung for
the first time in many months. I wonder if this is by chance or if other
people experienced the same?
--
You received this bug notification because you a
Ok, after updating to the latest BIOS the issue seems resolved for me.
I'm now also at an uptime of over 3 weeks, and before I could never get
past 1 week. I've updated the BIOS of my ASRock AB350 Pro4 AMD B350 to
3.20 with AGESA 1.0.0.6b.
I am currently running kernel 4.14.5 with CONFIG_RCU_NOCB_
I have the same crash as Rachel whenever I unplug the DVI from my NVidia
graphics card or switch the KVM to another monitor. I use Ubuntu 17.10
latest, with mutter 3.26.2-0ubuntu0.1 installed. This does not fix the
crash.
I also get the assertion:
meta_monitor_manager_get_logical_monitor_from_numb
I think its very very unlikely to have a different underlying cause, even
though I there is no guarantee. I assume that I am affected by the same problem
because:
(1) The problem manifests identical to other reports here
(2) The freeze happens particularly during idle times, not under heavy load
Its great that the frequency of freezes is reduced. But I guess many people
here expect a stable
system and can work with nothing less. Ryzen-Processors are attractive for
CI-systems, and I can
not have regular freezes in our CI. I think this is an all-or-nothing-issue,
and I still had a
freeze
I have compiled the current Ubuntu 17.10 kernel 4.13.0-17-generic with
CONFIG_RCU_NOCB_CPU
and boot option "rcu_nocbs=0-15" and just had a system freeze again. My System
is a Ryzen 7 1700X
on an ASrock AB350 Pro4 mainboard with 32GB Ram @3200.
I do not use the kernel option "processor.max_cstate=
None of the solutions above work for me. I don't have a dock, just the
headset jack on T440p.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1508826
Title:
[20ANCTO1WW, Realtek ALC3232, Black Headpho
I can reproduce this problem on Ubuntu Classic and Unity sessions. It
affects Matlab 2009b, 2010b and Fiji (an ImageJ clone). I can
temporarily fix the problem using "compiz --replace" or "gtk-window-
decorator --replace", but it will eventually come again, rendering Natty
almost unusable for me. P
29 matches
Mail list logo