Unfortunately I have to confirm that the workaround from #42 only makes the
hard freeze less frequent and doesn't solve it like I stated in #53.
I also have the impression that standby/resume increases the probability of a
freeze, but I just had one about one hour after a fresh new start.
--
After uptime 15 days, 10:34 with countless standby/resume cycles, I
think it is pretty safe to say that the solution from #42 works for me
too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798961
I just received Kernel 5.0.0-11-generic via Ubuntu update and the issue
seems to be solved :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822441
Title:
[Intel® HD Graphics 3000] Blank screen
Done: https://bugs.freedesktop.org/show_bug.cgi?id=110359
Thanks to all helping out!
** Bug watch added: freedesktop.org Bugzilla #110359
https://bugs.freedesktop.org/show_bug.cgi?id=110359
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@teresaejunior Yes, currently trying it, will report back!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798961
Title:
Random unrecoverable freezes on Ubuntu 18.10
To manage notifications about
Also with 4.19.26-generic there is the error:
[ 7.575] (EE) modeset(0): failed to set mode: Invalid argument
** Attachment added: "Xorg.0.log-4.19.26"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+attachment/5251780/+files/Xorg.0.log-4.19.26
--
You received this bug
So I tried a lot of kernels :-)
The latest it still works with was 4.19.25-generic (currently using it).
It fails starting with 4.19.26-generic.
I tried many versions older than 4.19.25-generic, they all worked, and
any version later than 4.19.26-generic failed as well.
So it seems something
Unfortunately I have to revoke my comment #44 - had again two freezes
with 4.18.0-16-generic in the last few days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798961
Title:
Random unrecoverable
Public bug reported:
Updated from kubuntu 18.10 to 19.04 beta without problems. After first
reboot, first the kubuntu logo, then just a blank screen, no login
screen. Switching to console and log in there possible. All seems fine,
including wlan etc.
systemd status sddm says sddm is running, any
For me on a DELL Latitude E5550 it seems the issue is solved since
update to 4.18.0-16-generic (kubuntu). Running for a week now with
several suspend/resume cycles - no more frost. Spring is coming :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just would like to add that I have the same problem about once a day
on a DELL Latitude E5550, usually a relatively short while after
resuming from standby. It never happens when I boot into the older
4.15.0-39-generic kernel.
On a Lenovo L420 that I have updated at the same time, I never had
I suppose this bug report is not relevant any more - it is very old, the
issue went away long time ago and there is a new major release of KDE
for a while now - setting it to invalid.
** Changed in: ubuntu
Status: Incomplete => Invalid
--
You received this bug notification because you
Just want to mention that after a recent update the L of KDE4
applications like Amarok is consistent again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514491
Title:
kubuntu desktop
I hope it is okay that I add some issues here that I think are related -
if not, please let me know and I'll create a separate bug.
There are some other L inconsistencies for me since upgrading from
15.10 to 16.04 Beta2:
- KDE4 applications like Amarok now use some other style
- Eclipse with
With the freezes I had it was not possible to "revive" from, all I could
do is long-press the power button.
So maybe the freezes you encounter are another issue, maybe this bug:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1384512
It is about KDE but sounds similar and might be related to the
Please ignore/delete this bug report. The upgrade was incomplete, some
packages were held back. After several more attempts to apt-get update
and apt-get upgrade, eventually the remaining packages were installed
and now all is fine.
Sorry for that!
--
You received this bug notification because
Sorry if it is obvious, but is the fix included in 5.2? The problem is
still present there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400730
Title:
libxext fills up .xsession-errors log files
I'd like like to correct some statements in my comment:
- Switching to XRender does not have an impact on the placement of dialogs and
windows.
- Sometimes the panel freezes, then .xsession-errors still fills up the /home
partition. But it happens only every now and then.
--
You received this
Pressing ALT+TAB allows me to cycle through the windows but does not
unfreeze the desktop once it is frozen on a Lenovo L420 with Intel i5
and Intel HD 3000 graphics with a dual-screen setup.
Switching from OpenGL 2.0 to 3.1 did not help with the freezes, but
switching to XRender did. Also some
Following your experience, I have disabled CPU Power Management and
PCI Express Power Management in the BIOS of my Lenovo L420.
I did not have a single freeze in one month now (before about once a
week), so I suppose this solved my freezing issues as well. The fact
that the freezes occurred only
I am not aware of any workaround and I wonder if our freezes are related
or if we have individual hardware issues. But I am pretty sure I did not
have theses issues before 13.10 on the same hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Unfortunately I still have this problem, by the time with kubuntu 14.04.
Often when the system is idling for some hours, it eventually freezes.
I again let Memtest86 running, it did 9 passes in more than 13 hours
without error, so it is probably not a memory issue.
There is usually an external
Can confirm that this is still not working on Kubuntu 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201180
Title:
Pressing power button turns off the PC ignoring the presence of
another
Thank you Joseph.
After running about one week without the bad memory module and another
week with a new 2nd 4GB module without any freeze I think we can assume
this bug is invalid :-)
Torsten
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Since about the final version of 13.10 (using it since Beta 2), my
Lenovo L420 which was running stable until then randomly hard
freezes/locks up about once a day while idling.
It never happens while I am using the PC, only when I am away. It
sometimes runs through a whole
I have done a memory test as suggested in
https://help.ubuntu.com/community/DebuggingSystemCrash - sorry for not
reading it earlier.
Errors were found at four addresses in the memory area of the second 4
GB module. After removing it and running with only the first 4 GB, no
more errors were found.
Rebuilding the libx264-123_0.123.2189+git35cf912-1ubuntu2 packages with
-fno-aggressive-loop-optimizations indeed solves the problem on 13.10,
there is no more segfault:
https://www.dropbox.com/sh/0o1bi2vzmp5p11o/vBzFd8nCgx
--
You received this bug notification because you are a member of Ubuntu
With kubuntu 13.10 Beta 2 and kernel 3.11.0-11-generic, the messages can
still be found in syslog, but I didn't experience the hanging mouse
pointer any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Application: python2 (0.5.7)
KDE Platform Version: 4.11.1
Qt Version: 4.8.4
Operating System: Linux 3.11.0-7-generic x86_64
Distribution: Ubuntu Saucy Salamander (development branch)
-- Information about the crash:
Erklären Sie bitte ganz genau, was Sie machten, als das Programm abstürzte.
The
Public bug reported:
In kubuntu 13.10, jockey-kde crashes immediately on startup.
In 13.04, with a Freecom/Wideview USB DVB/T stick connected, it worked just
fine, the driver for the device was listed and successfully installed.
** Affects: jockey (Ubuntu)
Importance: Undecided
** Summary changed:
- Crashes immediately on startup
+ jockey-kde crashes immediately on startup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1224171
Title:
jockey-kde crashes immediately on
I have a crash on 13.10, also segfault, but I don't know where exactly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/922603
Title:
software-properties-kde crashed with SIGSEGV in createClassType()
Does anyone know a workaround for this issue? I have this several times
an hour, sometimes every few minutes - very annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198274
Title:
Lenovo
I still have this issue on 13.04 with kernel 3.8.0-26-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198274
Title:
Lenovo l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost
sync
Thanks also from me Petr, no freeze the whole day so far, while there
was 5-20 each day before.
I'm glad we have a stable system again :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963736
Title:
Petr, I'd be interested in your amd64 package. FF and TB both are nearly
unusable, I'd be very happy for a solution!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963736
Title:
thunderbird and
Great, thanks for this hint! Nice to have the estimated remaining time
back.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-workspace in Ubuntu.
https://bugs.launchpad.net/bugs/395666
Title:
plasma_applet_battery widget doesn't
I am using KDE 4.9.3 and there is no estimated time information in the
popup. It was there in the previous release of Kubuntu, I think it was
KDE 4.8.x, and it worked pretty accurate, so it is a bit a shame that it
is missing now.
A side note: When clicking on the battery icon, the popup is
I can confirm that Start_Stop_Count doesn't increment any more, which is
nice, but Load_Cycle_Count still increments by about 1-10 per minute.
I set apm_battery = 254 in /etc/hdparm.conf now, which stops
Load_Cycle_Count from incrementing, so that is fine.
But isn't this the wrong solution? I
Sounds reasonable, and without wanting to turn this bug report into a
discussion thread: Are there some interesting values for apm_battery
between 128 and 254 to try out, to sort of find a good trade-off between
lots of load cycles vs. heads never being parked? I googled without much
success, it
After upgrading to kubuntu 12.04 with KDE 4.8.2, I don't experience this
problem any more.
I can use Eclipse and any other application the whole day without that
it freezes.
This version of kubuntu and KDE seems to be very stable in general.
Cheers,
Torsten
--
You received this bug
Adding apm_battery = 128 to /etc/hdparm.conf solves the problem also
on my old BenQ notebook - thanks for providing this solution!
I can say that also I am sometimes very frustrated about these kind of
bugs, that seem to come back ever so often after getting fixed.
But there is this great
With the official packages available at that time the desktop frequently
crashed and was almost unsuable:
https://bugs.kde.org/show_bug.cgi?id=272495
And by now I have the official packages, I suppose, and it is still the
same problem - restarting Eclipse three times per day and Lotus Notes
Public bug reported:
I have recently upgraded to KDE 4.7.4 from the PPA to get rid of constant
crashes of the Desktop. Since then, some of the applications I extensively use
throughout the day start to become extremely slow at some point after some
hours of use (it is more the GUI that seems
Compiz crashes always some 30 seconds after login
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/726500
Title:
compiz crashed with SIGSEGV in g_source_unref()
--
ubuntu-bugs mailing list
Hello Fabio,
I ran the given commands, please see below. It seems hibernate is
supported, just not offered by g-p-m?
Cheers,
Torsten
root@linus:~# dbus-send --session --print-reply
--dest=org.freedesktop.PowerManagement --type=method_call
--reply-timeout=6000 /org/freedesktop/PowerManagement
Public bug reported:
Binary package hint: bluez
This seems to be a regression.
When I start my notebook, bluetooth is disabled and I switch it on once Ubuntu
is started. Until some days ago, the bluetooth symbol appeared in the
notification area and my travel mouse worked after a few seconds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/713750
Title:
bluetoothd needs to be restarted to get bluetooth to work
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
48 matches
Mail list logo
