What could cause this glitch in gedit?
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I was casually working with my Ubuntu 18.04, when all of a sudden the desktop ceased to be responsive. I restarted the system and booted to a black screen with mouse pointer and the CPU fan going all guns blazing.
This thing happened to me before with 17.10 and as I described in my question here, this was completely unprovoked on my side. I did not do any installs or upgrades, so none of the answers to the questions linked as duplicates apply.
Elder Geek suggested that I check my harddrive for failures. I ran the SMART diagnosis and everything was OK.
Knowing that the only way out was to re-install the system, I did exactly that, only to find that the gedit text editor is behaving glitchy on resize and text editing. Kate, the other text editor, does not have this problem.
I checked my system logs, but I have no idea what any of that information means and if it could be the cause of this glitch.
14:34:48 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:47 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
14:34:37 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:36 wpa_supplicant: dbus: Failed to construct signal
14:34:34 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
14:34:34 kernel: MODSIGN: Couldn't get UEFI db list
14:34:34 kernel: Couldn't get size: 0x800000000000000e
14:34:34 kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Has anybody had a similar problem? Are these log messages benign, or could some of them have caused this glitch?
graphics 18.04 gedit
asked May 26 at 12:53
Martin Drozdik
1,01541626
add a comment |Â
up vote
0
down vote
favorite
I was casually working with my Ubuntu 18.04, when all of a sudden the desktop ceased to be responsive. I restarted the system and booted to a black screen with mouse pointer and the CPU fan going all guns blazing.
This thing happened to me before with 17.10 and as I described in my question here, this was completely unprovoked on my side. I did not do any installs or upgrades, so none of the answers to the questions linked as duplicates apply.
Elder Geek suggested that I check my harddrive for failures. I ran the SMART diagnosis and everything was OK.
Knowing that the only way out was to re-install the system, I did exactly that, only to find that the gedit text editor is behaving glitchy on resize and text editing. Kate, the other text editor, does not have this problem.
I checked my system logs, but I have no idea what any of that information means and if it could be the cause of this glitch.
14:34:48 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:47 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
14:34:37 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:36 wpa_supplicant: dbus: Failed to construct signal
14:34:34 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
14:34:34 kernel: MODSIGN: Couldn't get UEFI db list
14:34:34 kernel: Couldn't get size: 0x800000000000000e
14:34:34 kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Has anybody had a similar problem? Are these log messages benign, or could some of them have caused this glitch?
graphics 18.04 gedit
asked May 26 at 12:53
Martin Drozdik
1,01541626
1
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was casually working with my Ubuntu 18.04, when all of a sudden the desktop ceased to be responsive. I restarted the system and booted to a black screen with mouse pointer and the CPU fan going all guns blazing.
This thing happened to me before with 17.10 and as I described in my question here, this was completely unprovoked on my side. I did not do any installs or upgrades, so none of the answers to the questions linked as duplicates apply.
Elder Geek suggested that I check my harddrive for failures. I ran the SMART diagnosis and everything was OK.
Knowing that the only way out was to re-install the system, I did exactly that, only to find that the gedit text editor is behaving glitchy on resize and text editing. Kate, the other text editor, does not have this problem.
I checked my system logs, but I have no idea what any of that information means and if it could be the cause of this glitch.
14:34:48 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:47 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
14:34:37 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:36 wpa_supplicant: dbus: Failed to construct signal
14:34:34 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
14:34:34 kernel: MODSIGN: Couldn't get UEFI db list
14:34:34 kernel: Couldn't get size: 0x800000000000000e
14:34:34 kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Has anybody had a similar problem? Are these log messages benign, or could some of them have caused this glitch?
graphics 18.04 gedit
asked May 26 at 12:53
Martin Drozdik
1,01541626
I was casually working with my Ubuntu 18.04, when all of a sudden the desktop ceased to be responsive. I restarted the system and booted to a black screen with mouse pointer and the CPU fan going all guns blazing.
This thing happened to me before with 17.10 and as I described in my question here, this was completely unprovoked on my side. I did not do any installs or upgrades, so none of the answers to the questions linked as duplicates apply.
Elder Geek suggested that I check my harddrive for failures. I ran the SMART diagnosis and everything was OK.
Knowing that the only way out was to re-install the system, I did exactly that, only to find that the gedit text editor is behaving glitchy on resize and text editing. Kate, the other text editor, does not have this problem.
I checked my system logs, but I have no idea what any of that information means and if it could be the cause of this glitch.
14:34:48 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:47 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
14:34:37 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
14:34:36 wpa_supplicant: dbus: Failed to construct signal
14:34:34 kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
14:34:34 kernel: MODSIGN: Couldn't get UEFI db list
14:34:34 kernel: Couldn't get size: 0x800000000000000e
14:34:34 kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)
Has anybody had a similar problem? Are these log messages benign, or could some of them have caused this glitch?
graphics 18.04 gedit
asked May 26 at 12:53
Martin Drozdik
1,01541626
asked May 26 at 12:53
Martin Drozdik
1,01541626
asked May 26 at 12:53
Martin Drozdik
1,01541626
asked May 26 at 12:53
Martin Drozdik
1,01541626
1,01541626
1
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36
add a comment |Â
1
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36
1
1
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1040582%2fwhat-could-cause-this-glitch-in-gedit%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
See my answer at askubuntu.com/questions/838259/…
– heynnema
May 26 at 13:46
@heynnema Thank you! I deleted the file, rebooted, and the problem is gone!
– Martin Drozdik
May 26 at 16:13
@heynnema, I also have this spice error in my 18.04, but there are no .xinputrc in my machine. :(
– Cristiano
May 29 at 17:36