[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
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. -- 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 this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
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 Title: Random unrecoverable freezes on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822441]
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 after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlier works) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1822441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlie
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 Ubuntu. https://bugs.launchpad.net/bugs/1822441 Title: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 4.19.26 and later (but 4.19.25 and earlier works) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
@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 this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0
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 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 after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822441] Re: [Intel® HD Graphics 3000] Blank screen after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0
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 broke in 4.19.26-generic. ** Attachment added: "Xorg.0.log-4.19.26.old" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+attachment/5251779/+files/Xorg.0.log-4.19.26.old -- 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 after startup. Xorg reports "(EE) modeset(0): failed to set mode: Invalid argument" when using kernel 5.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
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 freezes on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822441] [NEW] Blank screen after startup
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 attempt to start KDE (including startkde) however fails with "could not connect to any x display". This happens with Kernel 5.0.0. Starting with 4.18.0-16-generic, the login screen comes up and all is fine. Anything I can contribute? Description:Ubuntu Disco Dingo (development branch) Release:19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Mar 30 21:51:04 2019 DistUpgraded: 2019-03-30 14:41:04,209 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: disco DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 4.18.0-16-generic, x86_64: installed acpi-call, 1.1.0, 5.0.0-8-generic, x86_64: installed tp_smapi, 0.43, 5.0.0-8-generic, x86_64: installed virtualbox, 6.0.4, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21dd] InstallationDate: Installed on 2017-07-07 (631 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 78545HG ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=ce827244-1d04-4bdd-99bf-d70675baefef ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to disco on 2019-03-30 (0 days ago) dmi.bios.date: 04/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET44WW (1.21 ) dmi.board.name: 78545HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad L420 dmi.product.name: 78545HG dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- 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: Blank screen after startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
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 the problem so far. -- 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 this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922022] Re: Applications freeze after several hours of extensive use
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922022 Title: Applications freeze after several hours of extensive use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/922022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514491] Re: kubuntu desktop inconsistency and integration issues: scrollbars. gtk3 button placement also not integrated
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 inconsistency and integration issues: scrollbars. gtk3 button placement also not integrated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-gtk/+bug/1514491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514491] Re: kubuntu desktop inconsistency and integration issues: scrollbars. gtk3 button placement also not integrated
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 GTK2 and Thunderbird now uses plus signs for tree node handles instead of rectangles - Eclipse with GTK3 has a dotted line at the lower and right window edges All of them looked consistent in 15.10 (besides Eclipse with GTK3 which looked kinda broken but looks much better now). Please see attached screenshot incl. one of Dolphin which looks fine of course (tree nodes, scrollbar). ** Attachment added: "kubuntu1610.png" https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/1514491/+attachment/4629380/+files/kubuntu1610.png -- 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 inconsistency and integration issues: scrollbars. gtk3 button placement also not integrated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/breeze-gtk/+bug/1514491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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 video driver, so maybe Unity suffers from the same issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1457692] Re: KWin frequent crashes after upgrade to Plasma 5.3
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 you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1457692 Title: KWin frequent crashes after upgrade to Plasma 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1457692/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1400730] Re: libxext fills up .xsession-errors log files
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1384512] Re: Plasma 5 frequent screen freezes
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 bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1384512 Title: Plasma 5 frequent screen freezes To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-packaging-next/+bug/1384512/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1384512] Re: Plasma 5 frequent screen freezes
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 animations like fading in/out popups/tooltips is now much smoother. And a lot of other things seem to work properly now, like dialogs correctly being placed on top, applications opening in the primary display and so on. Also, I had the issue with the giant .xsession-errors file before, which is gone now. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to Kubuntu PPA. https://bugs.launchpad.net/bugs/1384512 Title: Plasma 5 frequent screen freezes To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-packaging-next/+bug/1384512/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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 during idle (power management kicking in?) seems to confirm this. BIOS or kernel bugs? Glad I have a stable system again - Thanks for sharing! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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 screen connected via VGA, but I have seen the freeze also when running on battery with no external devices connected, that time while I was working. However, connecting an external screen prevents the system from suspending - for a reasoning that I can't follow - so this is why the system may idle for hours and eventually freeze, while normally it would suspend after half an hour. The syslog does not show anything besides a line of garbage at the point where it crashed: ul 20 18:40:01 linus CRON[5077]: (www-data) CMD ([ -x /usr/share/awstats/tools/update.sh ] /usr/share/awstats/tools/update.sh) Jul 20 18:40:01 linus CRON[5076]: (smmsp) CMD (test -x /etc/init.d/sendmail /usr/share/sendmail/sendmail cron-msp) Jul 20 18:40:01 linus sm-msp-queue[5093]: My unqualified host name (linus) unknown; sleeping for retry ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jul 20 20:26:39 linus rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=969 x-info=http://www.rsyslog.com;] start Jul 20 20:26:39 linus rsyslogd: rsyslogd's groupid changed to 103 Jul 20 20:26:39 linus rsyslogd: rsyslogd's userid changed to 101 Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpuset Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpu Jul 20 20:26:39 linus kernel: [0.00] Initializing cgroup subsys cpuacct Jul 20 20:26:39 linus kernel: [0.00] Linux version 3.13.0-32-generic (buildd@kissel) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 (Ubuntu 3.13.0-32.57-generic 3.13.11.4) Any advice on what I could do to find out what the reason for the freezes is? Cheers, Torsten ** Changed in: linux (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1201180] Re: Pressing power button turns off the PC ignoring the presence of another session manager
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 session manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1201180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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 Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] [NEW] Daily, random hard freeze/lock up during idle since 13.10
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 night, and sometimes it freezes when I leave it idle for just an hour or so. Once it froze while the screen was not blank yet, same situation. I have tried to disable power management in KDE and run without external screen and external harddisks, just on battery with nothing connected, then it also happens. The screen is usually blank, there is no reaction to either mouse or keyboard, switching to a console not possible, connection through VNC or SSD not possible. I need to hard-shutdown by long-pressing the power button. There is nothing in dmesg or syslog, it just ends and continues with the restarts. No kernel panics or something like that. Any advice on how to trace down the issue or similar experience? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-13-generic 3.11.0-13.20 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dode 2185 F pulseaudio Date: Wed Nov 27 14:06:00 2013 HibernationDevice: RESUME=UUID=3f651677-4186-4f48-b0f8-c20b56dbb2e8 InstallationDate: Installed on 2013-09-08 (80 days ago) InstallationMedia: Kubuntu 13.10 Saucy Salamander - Alpha amd64 (20130902.2) MachineType: LENOVO 78545HG MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=5aa9fd7d-cb84-4ab2-90f3-514b79fa541d ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8GET44WW (1.21 ) dmi.board.name: 78545HG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8GET44WW(1.21):bd04/12/2013:svnLENOVO:pn78545HG:pvrThinkPadL420:rvnLENOVO:rn78545HG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 78545HG dmi.product.version: ThinkPad L420 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255531] Re: Daily, random hard freeze/lock up during idle since 13.10
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. I will test for a week without the second module and report back if the freeze is solved with that. For anyone with a similar problem: It seems really worth running the memory test! With 8 GB it took just about 50 min for one complete pass. Just press (right) shift on startup to get the GRUB boot menu, and start the memory test from there. Cheers, Torsten -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255531 Title: Daily, random hard freeze/lock up during idle since 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1255531/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1241772] Re: Miscompilation with gcc 4.8 (segfault in x264_cqm_init)
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241772 Title: Miscompilation with gcc 4.8 (segfault in x264_cqm_init) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1241772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198274] Re: Lenovo l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
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. https://bugs.launchpad.net/bugs/1198274 Title: Lenovo l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1198274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224171] Re: Crashes immediately on startup
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 crash can be reproduced every time. -- Backtrace: Application: Jockey (python2), signal: Segmentation fault Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [KCrash Handler] #6 QMetaObject::indexOfProperty (this=0x7f97d7c0c300, name=0x7f97cab4d418 _kde_no_animations) at kernel/qmetaobject.cpp:738 #7 0x7f97df135030 in QObject::property (this=this@entry=0x21d53e0, name=0x7f97cab4d418 _kde_no_animations) at kernel/qobject.cpp:3737 #8 0x7f97caad5452 in Oxygen::Animations::registerWidget (this=0x1f2d550, widget=widget@entry=0x21d53e0) at ../../../kstyles/oxygen/animations/oxygenanimations.cpp:249 #9 0x7f97cab2b182 in Oxygen::Style::polish (this=0x1e9fbc0, widget=0x21d53e0) at ../../../kstyles/oxygen/oxygenstyle.cpp:209 #10 0x7f97dccbdcaa in QWidget::event (this=this@entry=0x21d53e0, event=event@entry=0x7fff308e7220) at kernel/qwidget.cpp:8472 #11 0x7f97dd05f5ce in QFrame::event (this=this@entry=0x21d53e0, e=0x7fff308e7220) at widgets/qframe.cpp:557 #12 0x7f97dd064630 in QLabel::event (this=this@entry=0x21d53e0, e=optimized out) at widgets/qlabel.cpp:1073 #13 0x7f97d6e8ca6b in KUrlLabel::event (this=0x21d53e0, event=optimized out) at ../../kdeui/widgets/kurllabel.cpp:329 #14 0x7f97d751da5b in sipKUrlLabel::event(QEvent*) () from /usr/lib/python2.7/dist-packages/PyKDE4/kdeui.so #15 0x7f97dcc6edfc in QApplicationPrivate::notify_helper (this=this@entry=0x1e32360, receiver=receiver@entry=0x21d53e0, e=e@entry=0x7fff308e7220) at kernel/qapplication.cpp:4567 #16 0x7f97dcc75470 in QApplication::notify (this=this@entry=0x1e028b0, receiver=receiver@entry=0x21d53e0, e=e@entry=0x7fff308e7220) at kernel/qapplication.cpp:4353 #17 0x7f97d6da59aa in KApplication::notify (this=0x1e028b0, receiver=0x21d53e0, event=0x7fff308e7220) at ../../kdeui/kernel/kapplication.cpp:311 #18 0x7f97d7889416 in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/python2.7/dist-packages/PyKDE4/kdeui.so #19 0x7f97df1228bd in QCoreApplication::notifyInternal (this=0x1e028b0, receiver=receiver@entry=0x21d53e0, event=event@entry=0x7fff308e7220) at kernel/qcoreapplication.cpp:946 #20 0x7f97dccbb04f in sendEvent (event=0x7fff308e7220, receiver=0x21d53e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #21 QWidget::ensurePolished (this=0x21d53e0) at kernel/qwidget.cpp:9723 #22 0x7f97dccbb099 in QWidget::ensurePolished (this=this@entry=0x21cf8e0) at kernel/qwidget.cpp:9732 #23 0x7f97dcc96a20 in QLayout::totalMinimumSize (this=0x21d4490) at kernel/qlayout.cpp:817 #24 0x7f97dccaaa00 in QWidget::minimumSizeHint (this=optimized out) at kernel/qwidget.cpp:8249 #25 0x7f97ddc9ce10 in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtGui.so #26 0x7f97dcc986c3 in qSmartMinSize (w=0x21cf8e0) at kernel/qlayoutengine.cpp:383 #27 0x7f97dd0b4ef8 in QSplitterPrivate::recalc (this=this@entry=0x21ba710, update=optimized out) at widgets/qsplitter.cpp:429 #28 0x7f97dd0b511e in QSplitterPrivate::insertWidget_helper (this=0x21ba710, index=2, widget=0x221d3e0, show=optimized out) at widgets/qsplitter.cpp:913 #29 0x7f97dda2f41b in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtGui.so #30 0x7f97df13abc1 in QObject::event (this=this@entry=0x2019630, e=e@entry=0x7fff308e7990) at kernel/qobject.cpp:1171 #31 0x7f97dccbe36b in QWidget::event (this=0x2019630, event=0x7fff308e7990) at kernel/qwidget.cpp:8845 #32 0x7f97dda2f5cb in ?? () from /usr/lib/python2.7/dist-packages/PyQt4/QtGui.so #33 0x7f97dcc6edfc in QApplicationPrivate::notify_helper (this=this@entry=0x1e32360, receiver=receiver@entry=0x2019630, e=e@entry=0x7fff308e7990) at kernel/qapplication.cpp:4567 #34 0x7f97dcc75470 in QApplication::notify (this=this@entry=0x1e028b0, receiver=receiver@entry=0x2019630, e=e@entry=0x7fff308e7990) at kernel/qapplication.cpp:4353 #35 0x7f97d6da59aa in KApplication::notify (this=0x1e028b0, receiver=0x2019630, event=0x7fff308e7990) at ../../kdeui/kernel/kapplication.cpp:311 #36 0x7f97d7889416 in sipKApplication::notify(QObject*, QEvent*) () from /usr/lib/python2.7/dist-packages/PyKDE4/kdeui.so #37 0x7f97df1228bd in QCoreApplication::notifyInternal (this=0x1e028b0, receiver=receiver@entry=0x2019630, event=event@entry=0x7fff308e7990) at kernel/qcoreapplication.cpp:946 #38 0x7f97dccbefab in sendEvent (event=0x7fff308e7990, receiver=0x2019630) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #39 QWidget::setParent (this=this@entry=0x221d3e0, parent=parent@entry=0x2019630, f=...) at kernel/qwidget.cpp:10280 #40 0x7f97dccbf44a in QWidgetPrivate::init
[Bug 1224171] [NEW] Crashes immediately on startup
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 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/1224171 Title: Crashes immediately on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1224171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1224171] Re: jockey-kde crashes immediately on startup
** 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 startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1224171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922603] Re: software-properties-kde crashed with SIGSEGV in createClassType()
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() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/922603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198274] Re: Lenovo l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
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 l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1198274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1198274] Re: Lenovo l520 psmouse serio4: TouchPad at isa0060/serio4/input0 lost sync at byte 1
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 at byte 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1198274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963736] Re: thunderbird and firefox freeze at random : must be killed and restarted
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: thunderbird and firefox freeze at random : must be killed and restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/963736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 963736] Re: thunderbird and firefox freeze at random : must be killed and restarted
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 firefox freeze at random : must be killed and restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/963736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 395666]
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 show Remaining Time when on battery To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/395666/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 395666]
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 partially obscured by the tooltip, and it is necessary to move the mouse away or wait to get rid of it. A really small annoyance, but still spoiling the usability a bit. -- 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 show Remaining Time when on battery To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/395666/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 952556] Re: [Precise] [Hardware-killer] HD restarts every few seconds
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 guess it is a good idea to park the heads after some inactivity, wouldn't it be better to prevent Linux from writing to disk so frequently, causing the heads to be quickly unparked? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952556 Title: [Precise] [Hardware-killer] HD restarts every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952556] Re: [Precise] [Hardware-killer] HD restarts every few seconds
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 seems to be all or nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952556 Title: [Precise] [Hardware-killer] HD restarts every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922022] Re: Applications freeze after several hours of extensive use
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922022 Title: Applications freeze after several hours of extensive use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/922022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952556] Re: [Precise] [Hardware-killer] HD restarts every few seconds
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 community - it didn't even take me 5 minutes to find 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/952556 Title: [Precise] [Hardware-killer] HD restarts every few seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hdparm/+bug/952556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922022] Re: Applications freeze after several hours of extensive use
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 (Eclipse based!) won't even start at all (which it does just fine under Gnome and Xfce). ** Bug watch added: KDE Bug Tracking System #272495 http://bugs.kde.org/show_bug.cgi?id=272495 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/922022 Title: Applications freeze after several hours of extensive use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/922022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 922022] [NEW] Applications freeze after several hours of extensive use
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 to be slow), use 100% CPU and if done quickly, they can be closed, otherwise they completely freeze within about a minute and keep on using 100% CPU. At least sometimes it is actually an X.org process that uses 100% CPU, not the actual application process. I have this with Eclipse which I use most, but have seen the exact same behaviour also with GIMP and Firefox. The problem did not occur before the upgrade to KDE 4.7.4, but it is still just a guess that it has something to do with that. The same behaviour shows on two different PCs with a clean installation of Kubuntu 11.10 and KDE 4.7.4 from the PPA. ** Affects: 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/922022 Title: Applications freeze after several hours of extensive use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/922022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726500] Re: compiz crashed with SIGSEGV in g_source_unref()
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713739] Re: Hibernate/suspend to disk is not available
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 org.freedesktop.PowerManagement.CanHibernate Error org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PowerManagement was not provided by any .service files root@linus:~# dbus-send --system --print-reply --dest=org.freedesktop.UPower --type=method_call --reply-timeout=6000 /org/freedesktop/UPower org.freedesktop.DBus.Properties.Get string:org.freedesktop.UPower string:CanHibernate method return sender=:1.15 - dest=:1.51 reply_serial=2 variant boolean true root@linus:~# gconftool-2 -g /apps/gnome-power-manager/general/can_hibernate »/apps/gnome-power-manager/general/can_suspend« wurde kein Wert zugewiesen (has no value assigned) root@linus:~# polkit-auth polkit-auth: Befehl nicht gefunden (Command not found) root@linus:~# hal-device | grep power_management.can_hibernate power_management.can_hibernate = true (bool) root@linus:~# pm-is-supported --hibernate; echo $? 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/713739 Title: Hibernate/suspend to disk is not available -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713750] [NEW] bluetoothd needs to be restarted to get bluetooth to work
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. Since a couple of days, after an update with the update-manager, the bluetooth symbol appears after switching the device on and the bluetooth-applet says it is on, but it is actually off. If I go to the settings, it says it is disabled and there is a huge button to enable it, but clicking it does nothing besides that the button gets disabled. When I kill the process /usr/sbin/bluetoothd --udev and start it again, bluetooth gets turned on/enabled and all works fine. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluez 4.87-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2 Uname: Linux 2.6.38-1-generic i686 Architecture: i386 Date: Sat Feb 5 19:06:17 2011 ExecutablePath: /usr/sbin/bluetoothd InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta i386 (20100901.1) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: BenQ Joybook S73 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic root=UUID=434bc615-3056-43ee-8b57-4fb157e47346 ro quiet splash vt.handoff=7 SourcePackage: bluez dmi.bios.date: 12/28/2006 dmi.bios.vendor: INSYDE dmi.bios.version: R4.00 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Joybook S73 dmi.board.vendor: BenQ dmi.board.version: 1.00 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrR4.00:bd12/28/2006:svnBenQ:pnJoybookS73:pvr1:rvnBenQ:rnJoybookS73:rvr1.00:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Joybook S73 dmi.product.version: 1 dmi.sys.vendor: BenQ hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:10:60:D0:20:0F ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:32811 acl:2110 sco:0 events:45 errors:0 TX bytes:586 acl:11 sco:0 commands:27 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 713750] Re: bluetoothd needs to be restarted to get bluetooth to work
-- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
