[Bug 1581522] Re: Font is garbled (in whole or in part) in dialog boxes in LibreOffice [Writer]
Even more alarming.. ** Attachment added: "LibreOffice2.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1581522/+attachment/4662139/+files/LibreOffice2.png ** Description changed: - EDIT: Note the later dialog box with mostly correct fonts (incorrect at - the top, not talking about the Chinese letter, which are a separate - issue, that I however do not recall previously, but think I know what - is..). Since the first dialog-box below, there was one or more - completely garbled: + EDIT: Note the later dialog box (that can't be degarbled by selecting) + with mostly correct fonts (incorrect at the top, not talking about the + Chinese letter, which are a separate issue, that I however do not recall + previously, but think I know what is..). Since the first dialog-box + below, there was one or more completely garbled: - - Note this dialog may not always display, because of special my condition* but in case it does not everyone might realize you can select the text to see it: + Note this dialog may not always display, because of special my + condition* but in case it does not everyone might realize you can select + the text to see it: "Either another instance of LibreOffice is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user 'qwerty' closes LibreOffice on host 'Vinnuryksugan'. Do you really want to continue?" * There is no simultaneous access, and note, I not reporting a problem with the text per se, just that it was unreadable. [I had just done a clean install to 16.04, but also copied my [/home] profile; Not aware of where font info is, it if came with the profile. I guess I didn't cleanly exit LibreOffice and it wouldn't have complained if my new machine had the same name. I used ubuntu-bug -w (from the command line, but previously from the dash, that bizarrely opens "Ubuntu Software"; previously I tried "ubuntu-bug libreoffice"). Should I report something more on these extra issues?] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 12:47:01 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-05-09 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: EDIT: Note the later dialog box (that can't be degarbled by selecting) with mostly correct fonts (incorrect at the top, not talking about the Chinese letter, which are a separate issue, that I however do not recall previously, but think I know what is..). Since the first dialog-box below, there was one or more completely garbled: - Note this dialog may not always display, because of special my + Note the first dialog may not always display, because of special my condition* but in case it does not everyone might realize you can select the text to see it: "Either another instance of LibreOffice is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user 'qwerty' closes LibreOffice on host 'Vinnuryksugan'. Do you really want to continue?" * There is no simultaneous access, and note, I not reporting a problem with the text per se, just that it was unreadable. [I had just done a clean install to 16.04, but also copied my [/home] profile; Not aware of where font info is, it if came with the profile. I guess I didn't cleanly exit LibreOffice and it wouldn't have complained if my new machine had the same name. I used ubuntu-bug -w (from the command line, but previously from the dash, that bizarrely opens "Ubuntu Software"; previously I tried "ubuntu-bug libreoffice"). Should I report something more on these extra issues?] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 12:47:01 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-05-09 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1581522] Re: Font is garbled in "first-use"-dialog in LibreOffice [Writer]
How it looked.. ** Attachment added: "LibreOffice.png" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1581522/+attachment/4662118/+files/LibreOffice.png ** Summary changed: - Font is garbled in "first-use"-dialog in LibreOffice [Writer] + Font is garbled (in whole or in part) in dialog boxes in LibreOffice [Writer] ** Description changed: - Note this dialog may not always display, because of special my - condition* but in case it does not everyone might realize you can select - the text to see it: + EDIT: Note the later dialog box with mostly correct fonts (incorrect at + the top, not talking about the Chinese letter, which are a separate + issue, that I however do not recall previously, but think I know what + is..). Since the first dialog-box below, there was one or more + completely garbled: + + + Note this dialog may not always display, because of special my condition* but in case it does not everyone might realize you can select the text to see it: "Either another instance of LibreOffice is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user 'qwerty' closes LibreOffice on host 'Vinnuryksugan'. Do you really want to continue?" - - * There is no simultaneous access, and note, I not reporting a problem with the text per se, just that it was unreadable. + * There is no simultaneous access, and note, I not reporting a problem + with the text per se, just that it was unreadable. [I had just done a clean install to 16.04, but also copied my [/home] profile; Not aware of where font info is, it if came with the profile. I guess I didn't cleanly exit LibreOffice and it wouldn't have complained if my new machine had the same name. I used ubuntu-bug -w (from the command line, but previously from the dash, that bizarrely opens "Ubuntu Software"; previously I tried "ubuntu-bug libreoffice"). Should I report something more on these extra issues?] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 12:47:01 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-05-09 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581522 Title: Font is garbled (in whole or in part) in dialog boxes in LibreOffice [Writer] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1581522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581522] [NEW] Font is garbled (in whole or in part) in dialog boxes in LibreOffice [Writer]
Public bug reported: EDIT: Note the later dialog box (that can't be degarbled by selecting) with mostly correct fonts (incorrect at the top, not talking about the Chinese letter, which are a separate issue, that I however do not recall previously, but think I know what is..). Since the first dialog-box below, there was one or more completely garbled: Note the first dialog may not always display, because of special my condition* but in case it does not everyone might realize you can select the text to see it: "Either another instance of LibreOffice is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user 'qwerty' closes LibreOffice on host 'Vinnuryksugan'. Do you really want to continue?" * There is no simultaneous access, and note, I not reporting a problem with the text per se, just that it was unreadable. [I had just done a clean install to 16.04, but also copied my [/home] profile; Not aware of where font info is, it if came with the profile. I guess I didn't cleanly exit LibreOffice and it wouldn't have complained if my new machine had the same name. I used ubuntu-bug -w (from the command line, but previously from the dash, that bizarrely opens "Ubuntu Software"; previously I tried "ubuntu-bug libreoffice"). Should I report something more on these extra issues?] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-core 1:5.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 13 12:47:01 2016 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2016-05-09 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581522 Title: Font is garbled (in whole or in part) in dialog boxes in LibreOffice [Writer] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1581522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I'm on Ubuntu 14.04.4 LTS Trusty. This report applies to a few weeks back (was at least 14.04.3). If I recall, I did get the input field (but months earlier I got no input field onces in a while). Sorry, I forgot to report, but then could reproduce easily, since memory was low. If I locked the screen, then I couldn't get back in, but realized if I got into a virtual terminal and killed one of the chrome processes, to make some room, I could get in. Since then I've given up on the Chrome browser and went back to Firefox. I'm not saying this has happened always with Chrome or it is the cause (or Firefox the solution), just that it is an example of a program that can fill the memory so it can be done manually reliably in other ways to reproduce my bug. Sorry if this is not the same bug, do say if you want it reported separately. I find it very likely that memory low could be the same problem, even when the symptom is slightly different. 1. Do you use a multi-head setup? I think not.. I do have another monitor, have set up dual in the past, now the other is unconnected, and the mouse pointer does not go "off" to either side. If yes, using just one monitor fixes the issue? Not sure, I must work with 2 screens 2. Can you reproduce all the time? Frequently every day, under conditions above. 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? I'm not sure if I'm using ldap, I guess Thunderbird may be, we do have ldap at work, not sure I'm using it for a "address book". [Seems strange that ldap would be the cause.., what could I likely be using else, that uses ldap?] Not sure what #115 is telling me to do or if asking for this info: ps -ef | grep -i screensaver qwerty 32042 30834 0 17:09 pts/27 00:00:00 grep --color=auto -i screensaver 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) Probably outdated.. less /var/log/auth.log.4.gz Feb 15 07:58:40 Vinnuryksugan pkexec: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Feb 15 07:58:40 Vinnuryksugan pkexec: pam_ck_connector(polkit-1:session): cannot determine display-device Feb 15 07:58:40 Vinnuryksugan pkexec[20380]: qwerty: Executing command [USER=root] [TTY=unknown] [CWD=/home/qwerty] [COMMAND=/usr/lib/update-notifier/package-system-locked] Feb 15 08:05:01 Vinnuryksugan CRON[20429]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:05:01 Vinnuryksugan CRON[20429]: pam_unix(cron:session): session closed for user root Feb 15 08:12:01 Vinnuryksugan CRON[20452]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:12:02 Vinnuryksugan CRON[20452]: pam_unix(cron:session): session closed for user root Feb 15 08:15:01 Vinnuryksugan CRON[20468]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:15:01 Vinnuryksugan CRON[20468]: pam_unix(cron:session): session closed for user root Feb 15 08:17:01 Vinnuryksugan CRON[20476]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:17:01 Vinnuryksugan CRON[20476]: pam_unix(cron:session): session closed for user root Feb 15 08:25:01 Vinnuryksugan CRON[20499]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:25:01 Vinnuryksugan CRON[20499]: pam_unix(cron:session): session closed for user root Feb 15 08:35:01 Vinnuryksugan CRON[20529]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:35:01 Vinnuryksugan CRON[20529]: pam_unix(cron:session): session closed for user root Feb 15 08:42:01 Vinnuryksugan CRON[20544]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:43:04 Vinnuryksugan CRON[20544]: pam_unix(cron:session): session closed for user root Feb 15 08:45:01 Vinnuryksugan CRON[20575]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:45:01 Vinnuryksugan CRON[20575]: pam_unix(cron:session): session closed for user root Feb 15 08:55:01 Vinnuryksugan CRON[20606]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 08:55:01 Vinnuryksugan CRON[20606]: pam_unix(cron:session): session closed for user root Feb 15 09:05:01 Vinnuryksugan CRON[20632]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 09:05:01 Vinnuryksugan CRON[20632]: pam_unix(cron:session): session closed for user root Feb 15 09:12:01 Vinnuryksugan CRON[20653]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 09:12:02 Vinnuryksugan CRON[20653]: pam_unix(cron:session): session closed for user root Feb 15 09:15:01 Vinnuryksugan CRON[20669]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 09:15:01 Vinnuryksugan CRON[20669]: pam_unix(cron:session): session closed for user root Feb 15 09:17:01 Vinnuryksugan CRON[20678]: pam_unix(cron:session): session opened for user root by (uid=0) Feb 15 09:17:01 Vinnuryksugan
[Bug 1482892] Re: Kernel PANIC often when turning WiFi off
This just happened again, and I believe I was running the latest (Ubuntu) kernel. No, not the upstream one.. It just seemed too much work.. and wouldn't prove anything if I can't get Ubuntu to freeze as that doesn't always happen.. I guess I really should get around to this as if it would happen again it would at least prove, not fixed upstream. The cause might however be in bcmwl (or an interaction between it in the kernel). I think the former here is *it*: lsmod |grep wl wl 6369280 0 cfg80211 540672 1 wl Installed files of bcmwl has no .ko but have files such as a Makefile: /usr/src/bcmwl-6.30.223.248+bdcom/patches/0015-add-support-for- Linux-3.18.patch [then this is a build a .ko, right? Do I need then linux-sources, I believe I don't and haven't had it installed in the past but I have it installed now, may have done that at some point, myself.. It hasn't been updated in a while, is at 3.19.0.17.16. I'm trying to learn thing so I could maybe be more helful in the future and/or not send bugus report if this one is it..] What I'm running now: uname -a Linux Ryksugan 3.19.0-27-generic #29-Ubuntu SMP Fri Aug 14 21:43:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux In case I forgot to restart after last kernel upgrade (I have Ksplice, but ages ago, it seemed to just stop working), then I would have been running /boot/initrd.img-3.19.0-26-generic Might only have worked pre-Nov 2014. It's just not something I had to do very often (or decided to try, to turn WiFi off, but it should always be safe). Possibly this might be even older and I just didn't try to trigger it. Very probably this might have to do with this, (and could very well has started around 3.17/3.18 timeframe): bcmwl (6.30.223.248+bdcom-0ubuntu2) vivid; urgency=medium * debian/dkms.conf.in, debian/patches/0014-add-support-for-Linux-3.17.patch, debian/patches/0015-add-support-for-Linux-3.18.patch: - Add support for Linux 3.17 (LP: #1358966). Credit for the patch goes to Brian Norris. - Add support for Linux 3.18 (LP: #1358966). Credit for the patch goes to Krzysztof Kolasa. -- Alberto Milone alberto.mil...@canonical.com Thu, 06 Nov 2014 18:43:27 +0100 bcmwl (6.30.223.248+bdcom-0ubuntu1) utopic; urgency=medium * New upstream release: (LP: #1342645) - This is an official public release from Broadcom. * debian/dkms.conf.in: - Drop patches for kernels 3.10 (now upstream) -- Robert Ancell robert.anc...@canonical.com Fri, 01 Aug 2014 11:09:43 +1200 ls -lrt /boot/initrd.img-3.1* -rw-r--r-- 1 root root 19976179 apr 10 17:20 /boot/initrd.img-3.13.0-47-generic * -rw-r--r-- 1 root root 21782845 apr 19 13:54 /boot/initrd.img-3.19.0-15-generic * -rw-r--r-- 1 root root 21737800 jún 3 21:54 /boot/initrd.img-3.19.0-20-lowlatency * -rw-r--r-- 1 root root 21782780 ágú 10 20:31 /boot/initrd.img-3.19.0-26-generic -rw-r--r-- 1 root root 21788996 ágú 15 18:24 /boot/initrd.img-3.19.0-27-generic marked with a star those I've not run in ages, just didn't clean up in case this doesn't resolve on day. The oldest or next oldest, I think worked at some point(I had more, but had to free space on /boot and deleted rarely used ones). ** Summary changed: - Kernel PANIC often when turning WiFi off + Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two before that one. ** Summary changed: - Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two before that one. + Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two, probably more, before that one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482892 Title: Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two, probably more, before that one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482892] Re: Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two, probably more, before that one
Strangely, grep 'Linux version' /var/log/syslog* /var/log/syslog:Aug 19 20:29:44 Ryksugan kernel: [0.00] Linux version 3.19.0-27-generic (buildd@lgw01-17) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #29-Ubuntu SMP Fri Aug 14 21:43:37 UTC 2015 (Ubuntu 3.19.0-27.29-generic 3.19.8-ckt5) [that is the kernel running *after* reboot/hitting the bug ones again.] Usually I see older restarts (wanted to confirm, seeing that one on previous boot, but none is showing up: ls -lrt /var/log/syslog* -rw-r- 1 syslog adm 157822 ágú 10 19:11 /var/log/syslog.7.gz -rw-r- 1 syslog adm 68255 ágú 14 12:18 /var/log/syslog.6.gz -rw-r- 1 syslog adm 89442 ágú 15 13:55 /var/log/syslog.5.gz -rw-r- 1 syslog adm 135946 ágú 16 17:03 /var/log/syslog.4.gz -rw-r- 1 syslog adm 30798 ágú 17 20:03 /var/log/syslog.3.gz -rw-r- 1 syslog adm9142 ágú 18 19:58 /var/log/syslog.2.gz -rw-r- 1 syslog adm 1229249 ágú 19 16:53 /var/log/syslog.1 -rw-r- 1 syslog adm 1574828 ágú 19 21:31 /var/log/syslog Seems I've had uptime, for 9 days.. unusual this long.. usually hit this or the other bugs/crashes I sent, more frequently: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473742 that one may have happened only ones or twice, but might be related? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482892 Title: Kernel PANIC often when turning WiFi off, on current 3.19.0-27-generic (see text, my be one older), happened before on previous kernel, and one or two, probably more, before that one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1075747] Re: Pydev workspaces become corrupted after loading them without Pydev installed
** Summary changed: - Pydev workspaces become corupted after loading them without Pydev installed + Pydev workspaces become corrupted after loading them without Pydev installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1075747 Title: Pydev workspaces become corrupted after loading them without Pydev installed To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse-eclipsers/+bug/1075747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1264554] Re: python3.4 autopkg test failures
The changelog says replacing the 512 bit dh key with a 2014 bit one coming from this: This is caused by a recent OpenSSL update in trusty-security. This needs https://hg.python.org/cpython/rev/1ad7c0253abe backported, I confirmed that this fixes the test. That commit says the same, but looking (closer at it) at the file it confirms, 2014 (an odd number) is a typo(s) for 1024. [I wander if the changelog here (or in Debian and Python) needs to be updated, or even if it is a possibility to change retroactively. I guess you could add a correction entry..] This also does: http://bugs.python.org/issue23844 and confirms the change was also made for Python 2.7. I can't see a similar update done to it (or [lib]python2.7-minimal). All python2.7 updates I see are from the month before. ** Bug watch added: Python Roundup #23844 http://bugs.python.org/issue23844 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1264554 Title: python3.4 autopkg test failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3.3/+bug/1264554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
I meant to add there, this bug I added, might be totally unrelated: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482892 It just hapened straight after this one, while I was trying what it says to get a change to report this one.. With THIS bug I didn't turn off the WiFi (manually), but suspend does that.. and I believe I didn't get a PANIC (no blinking lights). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
** Attachment added: syslog.3.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+attachment/4441759/+files/syslog.3.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] [NEW] Blank screen after suspend, unresposnsive
Public bug reported: Aug 7 23:45:36 Ryksugan NetworkManager[738]: info sleeping... Aug 7 23:45:36 Ryksugan NetworkManager[738]: info (eth0): device state change: unavailable - unmanaged (reason 'sleeping') [20 10 37] Aug 7 23:45:36 Ryksugan NetworkManager[738]: info NetworkManager state is now ASLEEP Aug 7 23:45:36 Ryksugan whoopsie[709]: [23:45:36] offline Aug 7 23:45:37 Ryksugan systemd[1]: Reached target Sleep. Aug 7 23:45:37 Ryksugan systemd[1]: Starting Sleep. Aug 7 23:45:37 Ryksugan systemd[1]: Starting Suspend... Aug 7 23:45:37 Ryksugan systemd-sleep[30096]: Suspending system... Aug 8 16:16:49 Ryksugan rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=697 x-info=http://www.rsyslog.com;] start Aug 8 16:16:49 Ryksugan rsyslogd: rsyslogd's groupid changed to 104 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: palli 1645 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 9 13:47:42 2015 HibernationDevice: RESUME=UUID=8bc9eb31-5629-4dc3-b989-1223eaf31529 InstallationDate: Installed on 2014-08-21 (352 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (124 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug package-from-proposed vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
** Attachment added: syslog.2.gz https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+attachment/4441758/+files/syslog.2.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
The syslog.1 is probably in no way helpful. The test I quoted at the original bug report at the time of suspend came from syslog.1, but now it is syslog.2.gz so I uploaded that one. Even that doesn't say much so I uploaded syslog.3gz if that is helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
** Description changed: + [Note, this does not happen on every suspend, but this is not the first + time. Might be unrelated: Often, but not always after suspend WiFi + doesn't work and I have to re-close the lid and wait a bit and open and + then it always works.] + Aug 7 23:45:36 Ryksugan NetworkManager[738]: info sleeping... Aug 7 23:45:36 Ryksugan NetworkManager[738]: info (eth0): device state change: unavailable - unmanaged (reason 'sleeping') [20 10 37] Aug 7 23:45:36 Ryksugan NetworkManager[738]: info NetworkManager state is now ASLEEP Aug 7 23:45:36 Ryksugan whoopsie[709]: [23:45:36] offline Aug 7 23:45:37 Ryksugan systemd[1]: Reached target Sleep. Aug 7 23:45:37 Ryksugan systemd[1]: Starting Sleep. Aug 7 23:45:37 Ryksugan systemd[1]: Starting Suspend... Aug 7 23:45:37 Ryksugan systemd-sleep[30096]: Suspending system... Aug 8 16:16:49 Ryksugan rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=697 x-info=http://www.rsyslog.com;] start Aug 8 16:16:49 Ryksugan rsyslogd: rsyslogd's groupid changed to 104 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: palli 1645 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: palli 1645 F pulseaudio CurrentDesktop: Unity Date: Sun Aug 9 13:47:42 2015 HibernationDevice: RESUME=UUID=8bc9eb31-5629-4dc3-b989-1223eaf31529 InstallationDate: Installed on 2014-08-21 (352 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.19.0-26-generic N/A - linux-backports-modules-3.19.0-26-generic N/A - linux-firmware 1.143 + linux-restricted-modules-3.19.0-26-generic N/A + linux-backports-modules-3.19.0-26-generic N/A + linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (124 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482995] Re: Blank screen after suspend, unresposnsive
#1482892 ** Attachment added: syslog.1 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+attachment/4441748/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482995 Title: Blank screen after suspend, unresposnsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1482995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482892] [NEW] Kernel PANIC often when turning WiFi off
Public bug reported: When opening lots of network connections and disconnecting from WiFi I get two light blinkning (CAPS LOCK light and the one to it's right) - assuming kernel PANIC. [As Google Chrome opens a lot of tabs, when starting, I've used the trick of disconnecting WiFi for a while (and sometimes killing Chrome processes, but not this time I believe, but it shouldn't matter), to get it to avoid OOM.] This is not the first time I've gotten a kernel PANIC this way or the only kernel (may be a few versions back). I assume this is a bug in the kernel (also), but also in (proprietary) wl: lsmod |grep wl wl 6369280 0 cfg80211 540672 1 wl syslog: Aug 8 16:59:18 Ryksugan dnsmasq[826]: setting upstream servers from DBus Aug 8 16:59:18 Ryksugan whoopsie[680]: [16:59:18] Cannot reach: https://daisy.ubuntu.com Aug 8 16:59:18 Ryksugan kernel: [ 2554.480178] cfg80211: World regulatory domain updated: Aug 8 16:59:18 Ryksugan kernel: [ 2554.480184] cfg80211: DFS Master region: unset Aug 8 16:59:18 Ryksugan kernel: [ 2554.480186] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Aug 8 16:59:18 Ryksugan kernel: [ 2554.480190] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Aug 8 16:59:18 Ryksugan kernel: [ 2554.480192] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Aug 8 16:59:18 Ryksugan kernel: [ 2554.480195] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm), (N/A) Aug 8 16:59:18 Ryksugan kernel: [ 2554.480197] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Aug 8 16:59:18 Ryksugan kernel: [ 2554.480200] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm), (N/A) Aug 8 16:59:18 Ryksugan NetworkManager[737]: info NetworkManager state is now DISCONNECTED Aug 8 16:59:18 Ryksugan NetworkManager[737]: warn Connection disconnected (reason -3) Aug 8 16:59:18 Ryksugan wpa_supplicant[792]: wlan0: CTRL-EVENT-SCAN-STARTED Aug 8 16:59:18 Ryksugan dbus[745]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Aug 8 16:59:18 Ryksugan NetworkManager[737]: info (wlan0): supplicant interface state: completed - disconnected Aug 8 16:59:18 Ryksugan systemd[1]: Starting Network Manager Script Dispatcher Service... Aug 8 16:59:18 Ryksugan dbus[745]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Aug 8 16:59:18 Ryksugan systemd[1]: Started Network Manager Script Dispatcher Service. Aug 8 16:59:18 Ryksugan nm-dispatcher: Dispatching action 'down' for wlan0 ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Aug 8 17:04:47 Ryksugan rsyslogd: [origin software=rsyslogd swVersion=7.4.4 x-pid=686 x-info=http://www.rsyslog.com;] start Aug 8 17:04:47 Ryksugan rsyslogd: rsyslogd's groupid changed to 104 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-26-generic 3.19.0-26.27 ProcVersionSignature: Ubuntu 3.19.0-26.27-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: palli 1645 F pulseaudio CurrentDesktop: Unity Date: Sat Aug 8 17:10:24 2015 HibernationDevice: RESUME=UUID=8bc9eb31-5629-4dc3-b989-1223eaf31529 InstallationDate: Installed on 2014-08-21 (351 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-26-generic N/A linux-backports-modules-3.19.0-26-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (124 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided
[Bug 1473742] [NEW] Can't resume from suspend with initrd.img-3.19.0-23-generic on Dell Inspiron 1525
Public bug reported: [Note I ran ubuntu-bug in the newest kernel I have, that works. I'll just file again if it needs to be the failing one..] Current initrd.img-3.19.0-23-generic, and older if I recall, also failed in the same way (had to delete old kernels to make space..): I can suspend and hear the fan go out and lights change, when going out of suspend at least something is working as the fan comes on but the screen is black. [I've updated lightdm recently and other things, that I thought might be the reason, but older initrd.img-3.19.0-15-generic and the one I'm running now, initrd.img-3.19.0-20-lowlatency, still work.] [Probably unrelated..: Recently (I guess in older kernels..) I've had suspend and resume work, but do not get WiFi after resume and then have to close the lid and after a second resume WiFi works..] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-20-lowlatency 3.19.0-20.20 ProcVersionSignature: Ubuntu 3.19.0-20.20-lowlatency 3.19.8 Uname: Linux 3.19.0-20-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: palli 1694 F...m pulseaudio /dev/snd/controlC0: palli 1694 F pulseaudio CurrentDesktop: Unity Date: Sun Jul 12 14:52:38 2015 HibernationDevice: RESUME=UUID=8bc9eb31-5629-4dc3-b989-1223eaf31529 InstallationDate: Installed on 2014-08-21 (324 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-lowlatency root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-20-lowlatency N/A linux-backports-modules-3.19.0-20-lowlatency N/A linux-firmware1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (96 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1473742 Title: Can't resume from suspend with initrd.img-3.19.0-23-generic on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1473742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453302] [NEW] Linux kernel freeze (it seems in current/3.19.0-17) on Dell Inspiron 1525
Public bug reported: First READ about how I deceived ubuntu-bug! I'm not sure it matters or what info ubuntu-bug collects, but I didn't do ubuntu-bug linux since it gave an error: Problem in linux-image-3.19.0-13-generic The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. I did ubuntu-bug Xorg just to get some collection of info, NOT saying xorg is the fault. Note that this bug report is NOT about that kernel but the most current (and maybe one or two others). Yesterday I wasn't having this problem with kernels (at least not the newest one I had not installed.. I may have had different problems, do not believe hardware broken though). $ ls -lrt /boot/initrd.img-3.1* -rw-r--r-- 1 root root 19976179 apr 10 17:20 /boot/initrd.img-3.13.0-47-generic -rw-r--r-- 1 root root 21779681 apr 11 14:54 /boot/initrd.img-3.19.0-13-generic -rw-r--r-- 1 root root 21782845 apr 19 13:54 /boot/initrd.img-3.19.0-15-generic -rw-r--r-- 1 root root 21733320 maí 8 20:26 /boot/initrd.img-3.19.0-15-lowlatency -rw-r--r-- 1 root root 21780289 maí 8 21:04 /boot/initrd.img-3.19.0-17-generic I believe I've been running 3.19.0-15-generic for the last few days. I just run the most recent one (usually - but not now because of the problems below). Today (this evening) I upgraded some stuff including the kernel. 3.19.0-17 does not boot up. I've tried several times and get a blank screen. I may have gotten something else, a splash-screen (not as far as login-screen), on the first try. DO not count on that as I may misremember. Then booting into 3.19.0-15-generic I could log in, so it seems the kernel above is the problem. Note I also upgraded more, say networking. AND now while I can log in, that kernel quickly froze (twice just after starting Chrome w/lots of tabs) - in a way I've never seen - the CAPS LOCK and the light to the RIGHT (NOT NUM LOCK to the left) where blinking in sync. I may have forgotten (or not?) to try a virtual terminal as this seemed a sure indication that something was wrong. [I also booted into just-installed 3.19.0-15-lowlatency and got the blinking lights.] Then I booted into 3.19.0-13 and am now for a much longer time in Chrome, so far no freeze.. [I was doing apt-get autoclean today, deleting kernels, so maybe I'm wrong about the exact version of the kernel I was running without problems, but at least all the info on kernels that do not work are right.] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompositorRunning: None CurrentDesktop: Unity Date: Fri May 8 21:50:41 2015 DistUpgraded: 2015-04-06 16:46:01,057 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: InstallationDate: Installed on 2014-08-21 (260 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UnitySupportTest: Error: [Errno 12] Cannot allocate memory UpgradeStatus: Upgraded to vivid on 2015-04-06 (32 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri May 8 21:43:05 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12631 vendor SEC xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64
[Bug 1453302] Re: Linux kernel freeze (it seems in current/3.19.0-17) on Dell Inspiron 1525
I was going to upload syslog with the correct info (what ubuntu-bug uploads seems only about since current boot). It seems the freeze is that severe (nothing on 3.19.0-17) or early that nothing gets appended to syslog. $ ls -lrt /var/log/syslog* .. -rw-r- 1 syslog adm 52942 maí 1 13:17 /var/log/syslog.2.gz -rw-r- 1 syslog adm 9474601 maí 8 20:01 /var/log/syslog.1 -rw-r- 1 syslog adm 3226101 maí 8 22:34 /var/log/syslog $ grep 'Linux version' /var/log/syslog May 8 21:15:48 Ryksugan kernel: [0.00] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3) May 8 21:25:42 Ryksugan kernel: [0.00] Linux version 3.19.0-15-lowlatency (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP PREEMPT Fri Apr 17 00:03:20 UTC 2015 (Ubuntu 3.19.0-15.15-lowlatency 3.19.3) May 8 21:39:24 Ryksugan kernel: [0.00] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3) May 8 21:40:21 Ryksugan kernel: [0.00] Linux version 3.19.0-15-generic (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP Thu Apr 16 23:32:37 UTC 2015 (Ubuntu 3.19.0-15.15-generic 3.19.3) May 8 21:43:04 Ryksugan kernel: [0.00] Linux version 3.19.0-13-generic (buildd@lamiak) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu12) ) #13-Ubuntu SMP Thu Apr 9 22:56:40 UTC 2015 (Ubuntu 3.19.0-13.13-generic 3.19.3) $ grep 'Linux version' /var/log/syslog.1 May 8 19:48:01 Ryksugan kernel: [0.00] Linux version 3.19.0-15-lowlatency (buildd@komainu) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu13) ) #15-Ubuntu SMP PREEMPT Fri Apr 17 00:03:20 UTC 2015 (Ubuntu 3.19.0-15.15-lowlatency 3.19.3) $ zgrep 'Linux version' /var/log/syslog.2.gz Uploading syslog in case it's helpful for the other kernels with blinking lights. ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453302/+attachment/4393956/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453302 Title: Linux kernel freeze (it seems in current/3.19.0-17) on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1453302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1452255] [NEW] Xorg freeze - on lockscreen
Public bug reported: What I know for sure: Locked screen - machine was frozen when I got back after minutes/seconds. Has happened several times before but does not happen most/all of the time. Of course very annoying (so I'll switch from nouveau to propriatary as a desperate move.. I really do not want to, would rather file bugs and see them fixed. Filing is what I can do, do not trust myself to fix or debug as random. I may move back if it helps with debugging). I wouldn't have thought Xorg was to blame (maybe it isn't) as machine only freezes this way when I lock screen (yes, I get oom for chrome and almost freezes, but can get to a virtual terminal - eventually, but that is different). Also I've reported other bug about lockscreen where password field if missing. This seems unrelated as here it is not. In hte other bug the mouse pointer may not have been frozen (I can't remember for sure). [I have dual-screen, not sure if important - seemed to be for other bug..] CAPS LOCK etc. lights are frozen and can't go to virtual screen. Still FLock light toggles, I think only the keyboard handles that.. Going over updates not installed, nothing important seems missing (as the update-manager shows *now*), I frequently do not update everything. E.g. libdrm-intel1 should not matter, I updated nouveau version recently: 2015-04-21 13:47:52 status installed libdrm-nouveau2:amd64 2.4.60-2~ubuntu14.04.1 and booted before getting the freeze but at least this was updated but not rebooted before the freeze: 2015-05-04 09:35:32 upgrade libmetacity-private0a:amd64 1:2.34.13-0ubuntu4 1:2.34.13-0ubuntu4.1 2015-05-04 09:35:33 upgrade metacity-common:all 1:2.34.13-0ubuntu4 1:2.34.13-0ubuntu4.1 Last rebootprior to freeze(?): $ who -b /var/log/wtmp.1 |tail -1 system boot 2015-04-28 14:11 While I get no response to (other) keys, I see that the kernel sees them in syslog (all relevant there starting w/nouveau):. May 6 09:55:01 Vinnuryksugan CRON[14155]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) May 6 10:05:01 Vinnuryksugan CRON[14305]: (root) CMD (command -v debian-sa1 /dev/null debian-sa1 1 1) May 6 10:10:27 Vinnuryksugan kernel: [677054.614186] nouveau E[compiz[2344]] fail ttm_validate May 6 10:10:27 Vinnuryksugan kernel: [677054.614191] nouveau E[compiz[2344]] validate vram_list May 6 10:10:27 Vinnuryksugan kernel: [677054.614201] nouveau E[compiz[2344]] validate: -12 May 6 10:10:28 Vinnuryksugan kernel: [677055.299662] nouveau E[ PFIFO][:01:00.0] read fault at 0x000774 [PAGE_NOT_PRESENT] from PGRAPH/GPC0/TEX on channel 0x001fcba000 [compiz[2344]] May 6 10:10:28 Vinnuryksugan kernel: [677055.299688] nouveau E[ PGRAPH][:01:00.0] TRAP ch 4 [0x001fcba000 compiz[2344]] May 6 10:10:28 Vinnuryksugan kernel: [677055.299699] nouveau E[ PGRAPH][:01:00.0] GPC0/TPC0/TEX: 0x8049 May 6 10:10:28 Vinnuryksugan kernel: [677055.299703] nouveau E[ PGRAPH][:01:00.0] GPC0/TPC1/TEX: 0x8049 May 6 10:12:01 Vinnuryksugan CRON[14409]: (root) CMD (export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin [ -x /usr/sbin/uptrack-upgrade ] /usr/sbin/uptrack-upgrade --cron) May 6 10:12:09 Vinnuryksugan kernel: [677156.263221] nouveau E[Xorg[1177]] failed to idle channel 0x0001 [Xorg[1177]] May 6 10:12:24 Vinnuryksugan kernel: [677171.270132] nouveau E[Xorg[1177]] failed to idle channel 0x0001 [Xorg[1177]] May 6 10:12:26 Vinnuryksugan kernel: [677173.271187] nouveau E[ PFIFO][:01:00.0] playlist update failed May 6 10:12:41 Vinnuryksugan kernel: [677188.277961] nouveau E[Xorg[1177]] failed to idle channel 0x [Xorg[1177]] May 6 10:12:56 Vinnuryksugan kernel: [677203.284882] nouveau E[Xorg[1177]] failed to idle channel 0x [Xorg[1177]] May 6 10:12:58 Vinnuryksugan kernel: [677205.285829] nouveau E[ PFIFO][:01:00.0] channel 2 [Xorg[1177]] kick timeout May 6 10:12:58 Vinnuryksugan kernel: [677205.286008] nouveau W[ PFIFO][:01:00.0] INTR 0x0100: 0x000d May 6 10:13:00 Vinnuryksugan kernel: [677207.286827] nouveau E[ PFIFO][:01:00.0] playlist update failed May 6 10:13:04 Vinnuryksugan colord: device removed: xrandr-Dell Inc.-DELL P2312H-YJ3JX33IAFJM May 6 10:13:04 Vinnuryksugan colord: device removed: xrandr-Dell Inc.-DELL P2312H-YJ3JX33IAF8M May 6 10:13:04 Vinnuryksugan colord: Profile removed: icc-9b9c44d46f4e90a2402855cc59555af8 May 6 10:13:04 Vinnuryksugan colord: Profile removed: icc-3c48fbaae41e31eb84074e6302c31a9d May 6 10:13:05 Vinnuryksugan gnome-session[2135]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.#012 May 6 10:13:06 Vinnuryksugan gdm-simple-slave[1107]: Child process 1177 was already dead. May 6 10:13:06 Vinnuryksugan gdm-simple-slave[1107]: GLib: Source ID 4 was not found when attempting to remove it May 6 10:13:06 Vinnuryksugan gdm-simple-slave[1107]: GLib-GObject: g_object_ref: assertion
[Bug 1452255] Re: Xorg freeze - on lockscreen
** Attachment added: Shuold show what I updated after the boot (but not still in effect) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452255/+attachment/4392194/+files/dpkg.log.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1452255 Title: Xorg freeze - on lockscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1452255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451264] Re: update-manager stopped in the middle, probably because of suspend or sleep (not network down)
Note, I ran update-manager on May 1, since then have had oom as dmesg show, may have had then also, that could have triggered this. Just do not remember or noticed then what was happening. oom are frequent.. Still not sure it happened then. syslog would show, just seems I probably can't upload.. dmesg too old to see? and doesn't show dates.. Why is syslog not uploaded.. by default? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451264 Title: update-manager stopped in the middle, probably because of suspend or sleep (not network down) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451264] Re: update-manager stopped in the middle, probably because of suspend or sleep (not network down)
** Attachment added: syslog.1 https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+attachment/4390336/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451264 Title: update-manager stopped in the middle, probably because of suspend or sleep (not network down) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451264] Re: update-manager stopped in the middle, probably because of suspend or sleep (not network down)
** Attachment added: _usr_bin_apt-extracttemplates.0.crash https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+attachment/4390337/+files/_usr_bin_apt-extracttemplates.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451264 Title: update-manager stopped in the middle, probably because of suspend or sleep (not network down) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451264] Re: update-manager stopped in the middle, probably because of suspend or sleep (not network down)
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+attachment/4390335/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451264 Title: update-manager stopped in the middle, probably because of suspend or sleep (not network down) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451264] [NEW] update-manager stopped in the middle, probably because of suspend or sleep (not network down)
Public bug reported:
Just the facts (I wrote an even longer bug-report and launchpad ate
it..):
ubuntu-bug asked if this was related to version update. I said no -
should I have said yes? Note, I've used update-manager a few times
without this and never happened in 12.04 and older I've used over the
years.
Preconfiguring packages ...
Preconfiguring packages ...
Preconfiguring packages ...
(Reading database ... 306131 files and directories currently installed.)
Preparing to unpack .../libudev1_219-7ubuntu4_i386.deb ...
De-configuring libudev1:amd64 (219-7ubuntu3) ...
Unpacking libudev1:i386 (219-7ubuntu4) over (219-7ubuntu3) ...
Preparing to unpack .../libudev1_219-7ubuntu4_amd64.deb ...
Unpacking libudev1:amd64 (219-7ubuntu4) over (219-7ubuntu3) ...
Setting up libudev1:amd64 (219-7ubuntu4) ...
Setting up libudev1:i386 (219-7ubuntu4) ...
Processing triggers for libc-bin (2.21-0ubuntu4) ...
(Reading database ... 306131 files and directories currently installed.)
Preparing to unpack .../udev_219-7ubuntu4_amd64.deb ...
Unpacking udev (219-7ubuntu4) over (219-7ubuntu3) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for systemd (219-7ubuntu3) ...
Setting up udev (219-7ubuntu4) ...
^[[Csdlsdlfj
[As show could type in, even days later. Didn't press CTRL-C aor
anything..]
[Off topic?: Since maybe this time (I think I was also updating network-
manager), WiFi-network shows no network, still there is network.. not
sure if/how it has to do with udev.]
$ ps -ef |grep update-manager
palli 9989 1314 0 maí01 ? 00:02:55 /usr/bin/python3
/usr/bin/update-manager
$ ps -ef |grep 9989
palli 9989 1314 0 maí01 ? 00:02:55 /usr/bin/python3
/usr/bin/update-manager
palli14105 9989 0 maí01 ? 00:00:00 [debconf-communi] defunct
$ ls -lrt /var/crash/
total 304
-rw-r- 1 root whoopsie 117092 maí 1 14:20
_usr_bin_apt-extracttemplates.0.crash
-rw-rw-r-- 1 palliwhoopsie 0 maí 1 14:33
_usr_lib_chromium-browser_chromium-browser.1000.upload
-rw--- 1 whoopsie whoopsie 0 maí 1 14:37
_usr_lib_chromium-browser_chromium-browser.1000.uploaded
-rw-r- 1 palliwhoopsie 188148 maí 3 20:16
_usr_lib_chromium-browser_chromium-browser.1000.crash
$ sudo strace -p 9989
Process 9989 attached
restart_syscall(... resuming interrupted call ...
[Pressed enter twice when there was a small (1 sec?) delay and added this text
there.]
) = 1
recvmsg(6, {msg_name(0)=NULL, msg_iov(1)=[{\241
\366\304\7\0`\3`\1\0\0m\1\0\0\311\0\1\0\7\0`\3\0\0\0\0\0\0\0\0, 4096}],
msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(6, 0x7ffda2fa13c0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=6, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=6,
revents=POLLOUT}])
writev(6, [{\31\0\v\0\200\0\0\0\0\0\30\0!
\0\0\200\0\0\0`\1\0\0m\1\0\0\311\0\1\0..., 44}, {NULL, 0}, {, 0}], 3) = 44
recvmsg(6, 0x7ffda2fa1270, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(6, 0x7ffda2fa13a0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN},
{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=77, events=POLLIN}, {fd=82,
events=POLLIN}], 7, 4294967295
[Pressed enter twice when there was a small (1 sec?) delay and added this text
there.]
) = 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL, msg_iov(1)=[{\241
\367\304\7\0`\3`\1\0\0m\1\0\0\312\0\1\0\7\0`\3\0\0\0\0\0\0\0\0, 4096}],
msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(6, 0x7ffda2fa13c0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=6, events=POLLIN|POLLOUT}], 1, 4294967295) = 1 ([{fd=6,
revents=POLLOUT}])
writev(6, [{\31\0\v\0\200\0\0\0\0\0\30\0!
\0\0\200\0\0\0`\1\0\0m\1\0\0\312\0\1\0..., 44}, {NULL, 0}, {, 0}], 3) = 44
recvmsg(6, 0x7ffda2fa1270, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(6, 0x7ffda2fa13a0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN},
{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=77, events=POLLIN}, {fd=82,
events=POLLIN}], 7, 4294967295) = 1 ([{fd=6, revents=POLLIN}])
recvmsg(6, {msg_name(0)=NULL,
msg_iov(1)=[{U\2\370\304A\17\\\24\3\24\4\0\20\0\0\0\0\0\0\24\24\24\24\24\0\0\3\37%\2\0\0,
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(6, 0x7ffda2fa13c0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(6, 0x7ffda2fa13a0, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}, {fd=6, events=POLLIN},
{fd=11, events=POLLIN}, {fd=12, events=POLLIN}, {fd=77, events=POLLIN}, {fd=82,
events=POLLIN}], 7, 4294967295^CProcess 9989 detached
detached ...
[I guess because defunct:]
$ sudo strace -p 14105
strace: attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted
Could not attach to process.
[Bug 1451264] Re: update-manager stopped in the middle, probably because of suspend or sleep (not network down)
Trying to upload _usr_bin_apt-extracttemplates.0.crash from /var/crash Only upload I can think of - helpful(?) I get this (and probably why first bug-report was eaten.. maybe a worse bug (in launchpad) than this one..): This webpage is not available Hide details The webpage at https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+addcomment might be temporarily down or it may have moved permanently to a new web address. Error code: ERR_ACCESS_DENIED Also this one, unrelated I thik was suggested: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1045252 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451264 Title: update-manager stopped in the middle, probably because of suspend or sleep (not network down) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1451264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 18711] Re: ethernet problem
** Summary changed: - ehernet problem + ethernet problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/18711 Title: ethernet problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/18711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443906] [NEW] Xorg freeze
Public bug reported: [I reported with ubuntu-bug, seems ok, and provides same info as ubuntu-bug xorg (as I then chose xorg)?] I locked the screen (yes, I have dual screen setup) and when coming back seconds/minutes later the pointer was frozen and I could not type in a password. Note, I see the password prompt [e.g. not (fully) similar to a bug (#1311316]) I've reported previously, that is supposed to be fixed, but I get e-mails saying it isn't..]. Here, at work in 14.04, all details are clear in memory still except for (and see about 15.04 below): [From memory I tried and failed to go to a virtual terminal, in case I misremember, I think I at least confirmed CAPS LOCK light not working.] After restart I got a (apport) dialog box about X failed. Note, I tried (after opening chrome) to use it to finish using that dialog box to send the error but didn't get the web-report I expected (like I'm filling out now) or any confirmation, so I used ubuntu-bug manually as I wasn't sure you get the info otherwise. I wouldn't know for sure that this freeze is because of Xorg and still do not know for sure, just seems so based on the auto dialog and report as such. What I can speculate about, if this is a new bug it may even come from vivid/15.04 (what has been backported recently?) as I've gotten a freeze (same or possibly only similar symptoms) at home with it. Note there, I do not have dual screens as it is a laptop. There the computer may have suspended. I do not recall if this only happened there when closing lid/suspend or even without. The screen may have been black can't remember all details at least it was frozen and required a reboot.. At home I have Intel, here Nvidia Quadro graphics. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-49.81-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 14 10:48:29 2015 DistUpgraded: 2015-03-19 11:34:13,727 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0835] InstallationDate: Installed on 2014-08-26 (230 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision T1650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to trusty on 2015-03-19 (25 days ago) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X9M3X dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1650 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 14 10:44:57 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 freeze trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1443116] [NEW] Xorg crash(?) (probably out of memory)
Public bug reported: If memory runs out, maybe not much can be done, but I believe this has not happened to me in older Ubuntu versions: Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure: order:0, mode:0xa00d4 Apr 12 14:29:51 Ryksugan kernel: [15064.494063] CPU: 0 PID: 792 Comm: Xorg Tainted: PW OE 3.19.0-13-generic #13-Ubuntu Apr 12 14:29:51 Ryksugan kernel: [15064.494065] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009 Apr 12 14:29:51 Ryksugan kernel: [15064.494067] 8800d784f618 817c2205 88011fc0fd78 Apr 12 14:29:51 Ryksugan kernel: [15064.494071] 000a00d4 8800d784f6a8 8117f148 8800d784f698 Apr 12 14:29:51 Ryksugan kernel: [15064.494074] 0001 0042 88011fff8e38 Apr 12 14:29:51 Ryksugan kernel: [15064.494078] Call Trace: At about 14:30 I felt the machine sluggish and I knew chromium-browser had been eating up memory (4 GB RAM and 4 GB SSD swap, have seen it or parts of it get killed before without this result). [In the past I've had trouble, usually could do unity --replace in virtual console.] [Note, after] Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page allocation failure: order:0, mode:0xa00d4 [Note before and all this probably unrelated, last chrome error before, /var/log/syslog.1 in reverse order:] Apr 12 14:14:35 Ryksugan kernel: [14148.682087] Out of memory: Kill process 13674 (chromium-browse) score 381 or sacrifice child .. Apr 12 14:04:24 Ryksugan kernel: [13537.199125] traps: chromium-browse[13500] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda1791f8 error:0 in libv8.so[7f c6d3d34000+5dc000] Apr 12 14:04:25 Ryksugan kernel: [13538.257833] traps: chromium-browse[13462] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda17ab68 error:0 in libv8.so[7f c6d3d34000+5dc000] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 12 14:51:03 2015 DistUpgraded: 2015-04-06 16:46:01,057 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022f] Subsystem: Dell Device [1028:022f] InstallationDate: Installed on 2014-08-21 (233 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-06 (5 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 12 14:30:42 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12631 vendor SEC xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash ubuntu vivid ** Attachment added: syslog.1 https://bugs.launchpad.net/bugs/1443116/+attachment/4373177/+files/syslog.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443116 Title: Xorg crash(?) (probably out of
[Bug 1443116] Re: Xorg crash (probably out of memory)
** Attachment added: Really?: Server terminated successfully (0). Closing log file https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373204/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443116 Title: Xorg crash(?) (probably out of memory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443116] Re: Xorg crash (probably out of memory)
** Attachment added: Just in case, seems this only shows correct startup after crash https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373205/+files/Xorg.0.log ** Summary changed: - Xorg crash (probably out of memory) + Xorg crash(?) (probably out of memory) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443116 Title: Xorg crash(?) (probably out of memory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443116] Re: Xorg crash (probably out of memory)
** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+attachment/4373203/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443116 Title: Xorg crash(?) (probably out of memory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1443116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443116] Re: Xorg crash(?) (probably out of memory)
[Not sure what (mesa) package to tag, there is a gnome-session[-bin] on likely
(more so than mesa that is not included in logs). Gnome-session without -bin
ending isn't even installed (GNOME3).]
Thanks for clarifying, I think you are saying, about here is the first
real error:
Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed:
Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App
'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop'
exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App
'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop'
respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required
component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail
whale is dead. Sorry
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We
failed, but the fail whale is dead. Sorry
[Then previous (allocation) failure(s) weren't really failures, that
is, the processes handle them? At least Xorg, also compiz?]
[One thing first, if this can't be fixed for sure, even Windows had a
virtual memory low dialog box warning, years ago when I used it.
Probably easy to make for Linux, might be available as an optional
package, but should it be built in?]
Since gnome-session failed with intel_do_flush_locked failed, does
that mean this has to do with drivers (Intel graphics)? Would other GPUs
(possibly) handle better?
Good to know that X itself should be pretty robust against oom
implying oom can be survived and should be for all components such as,
mesa, ngome-session[-bin], compiz[-core], drivers (and possibly even
chrome..).
[I feel at least the Linux kernel should. Yes, it didn't really fail
here, but sometimes thrashing has been a real problem and even getting
to virtual terminal is impossible or very slow because of thrashing or
something. I feel the kernel should hold up better so I can at least go
in and kill stuff..]
If compiz[-core] is for sure not the package (with compiz.desktop) with
a problem, but possibly also a package with a problem, should I report
that or can I add it too here?
Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure:
order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.740973] compiz: page allocation
failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page
allocation failure: order:0, mode:0xa00d4
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744173] chromium-browse invoked
oom-killer: gfp_mask=0x0, order=0, oom_score_adj=200
Apr 12 14:30:37 Ryksugan kernel: [15110.744176] chromium-browse
cpuset=session-c2.scope mems_allowed=0
..
Apr 12 14:30:37 Ryksugan kernel: [15110.744808] Out of memory: Kill process
13574 (chromium-browse) score 364 or sacrifice child
Apr 12 14:30:37 Ryksugan kernel: [15110.744813] Killed process 13574
(chromium-browse) total-vm:1642476kB, anon-rss:392980kB, file-rss:3536kB
Apr 12 14:30:38 Ryksugan gnome-session[1509]: intel_do_flush_locked failed:
Cannot allocate memory
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Loading
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: compiz (core) - Info: Starting
plugin: core
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App
'compiz.desktop' exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop'
exited with code 1
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: WARNING: App
'compiz.desktop' respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: WARNING: App 'compiz.desktop'
respawning too quickly
Apr 12 14:30:39 Ryksugan gnome-session[1509]: Unrecoverable failure in required
component compiz.desktop
Apr 12 14:30:39 Ryksugan gnome-session[1509]: CRITICAL: We failed, but the fail
whale is dead. Sorry
Apr 12 14:30:39 Ryksugan gnome-session[1509]: gnome-session[1509]: CRITICAL: We
failed, but the fail whale is dead. Sorry
Apr 12 14:30:39 Ryksugan org.ayatana.bamf[1401]: ** (bamfdaemon:1435): WARNING
**: Got an X error: BadWindow (invalid Window parameter)
Apr 12 14:30:39 Ryksugan pulseaudio[15446]: [pulseaudio] main.c:
User-configured server at
{f94f7f1731f6b57488f4027d53f78730}unix:/run/user/1000/pulse/native, which
appears to be local. Probing deeper.
Apr 12 14:30:39 Ryksugan gnome-session[1509]: (nm-applet:1727):
GLib-GObject-WARNING **: The property GtkSettings:gtk-color-palette is
deprecated and shouldn't be used anymore. It will be removed
[Bug 1443116] Re: Kicked out of desktop (gnome-session failed I'm told) (probably out of memory)
Since gnome-session failed with intel_do_flush_locked failed, does that mean this has to do with drivers (Intel graphics)? Would other GPUs (possibly) handle better? Thinking about this more, yes, I think Wilson is blaming intel_do_flush_locked=mesa. I think of mesa as 3D, but it is the project with (also) open source drivers? Still not sure what is the right package, xserver-xorg-video-intel (or something like libgl1-mesa- dri, not sure about intricate details of mesa, but none of them drivres or relevant?)? [Assume Intel [..] i965=GM965/GL960] 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1443116 Title: Kicked out of desktop (gnome-session failed I'm told) (probably out of memory) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1443116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1443116] Re: Kicked out of desktop (gnome-session failed I'm told) (probably out of memory)
Not sure about this. This package and/or gnome-session (and/or compiz)? ** Package changed: ubuntu = xserver-xorg-video-intel (Ubuntu) ** Description changed: - [Update, see comment #5 and my response at #6.] + [Update, see first comment #7 and #8 (or first comment #5 and my + response at #6).] If memory runs out, maybe not much can be done, but I believe this has not happened to me in older Ubuntu versions: Apr 12 14:29:51 Ryksugan kernel: [15064.494054] Xorg: page allocation failure: order:0, mode:0xa00d4 Apr 12 14:29:51 Ryksugan kernel: [15064.494063] CPU: 0 PID: 792 Comm: Xorg Tainted: PW OE 3.19.0-13-generic #13-Ubuntu Apr 12 14:29:51 Ryksugan kernel: [15064.494065] Hardware name: Dell Inc. Inspiron 1525 /0U990C, BIOS A17 10/27/2009 Apr 12 14:29:51 Ryksugan kernel: [15064.494067] 8800d784f618 817c2205 88011fc0fd78 Apr 12 14:29:51 Ryksugan kernel: [15064.494071] 000a00d4 8800d784f6a8 8117f148 8800d784f698 Apr 12 14:29:51 Ryksugan kernel: [15064.494074] 0001 0042 88011fff8e38 Apr 12 14:29:51 Ryksugan kernel: [15064.494078] Call Trace: At about 14:30 I felt the machine sluggish and I knew chromium-browser had been eating up memory (4 GB RAM and 4 GB SSD swap, have seen it or parts of it get killed before without this result). [In the past I've had trouble, usually could do unity --replace in virtual console.] [Note, after] Apr 12 14:30:37 Ryksugan kernel: [15110.743287] chromium-browse: page allocation failure: order:0, mode:0xa00d4 [Note before and all this probably unrelated, last chrome error before, /var/log/syslog.1 in reverse order:] Apr 12 14:14:35 Ryksugan kernel: [14148.682087] Out of memory: Kill process 13674 (chromium-browse) score 381 or sacrifice child .. Apr 12 14:04:24 Ryksugan kernel: [13537.199125] traps: chromium-browse[13500] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda1791f8 error:0 in libv8.so[7f c6d3d34000+5dc000] Apr 12 14:04:25 Ryksugan kernel: [13538.257833] traps: chromium-browse[13462] trap invalid opcode ip:7fc6d4201fc9 sp:7ffcda17ab68 error:0 in libv8.so[7f c6d3d34000+5dc000] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 12 14:51:03 2015 DistUpgraded: 2015-04-06 16:46:01,057 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:022f] Subsystem: Dell Device [1028:022f] InstallationDate: Installed on 2014-08-21 (233 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 1525 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to vivid on 2015-04-06 (5 days ago) dmi.bios.date: 10/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150330-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sun Apr 12 14:30:42 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12631 vendor SEC xserver.version:
[Bug 1441891] Re: Can't login after upgrade to 15.04 on Dell Inspiron 1525
[See next comment, this probably redundant.] After upgrading to the kernel that works on first use I opened synaptic and without doing anything I got a crash report: Sorry, a problem occurred while installing software. Package: linux-kernel-image-extra-3.19.0-13-generic 3.19.0-13-13 I assume this is just a relic from an update problem I had (No space on device /boot) pre-boot (and opening synaptic didn't trigger the dialog box). Since I got No space (and from memory image-extra not mentioned ,but might have been also) I reinstalled all kernel related after freeing space first. It seemed to go well. I assume I can ignore this error. At least I do not see a problem so far (not sure if extra is needed or what it's for exactly..) When closing the dialog just now I got: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/798414 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441891] Re: Can't login after upgrade to 15.04 on Dell Inspiron 1525
About bug link above, I fully understand how /boot can fill up, but can't it just not under / (not a small partition)? Would that have happened with a new install (not update)? Size of/separate /boot may have been self-inflicted. I do not remember any more if I chose it/its size. Related, some recommend separate /home (better for reinstallations). That one is under / and I do not worry too much, not sure I agree with separation. Any policy or default on this in Ubuntu? Has it changed lately? May or may not have implications for full-disk encryption? I guess you can live with all such decisions for long across many updates.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441891] Re: Can't login after upgrade to 15.04 on Dell Inspiron 1525
Note, original problem of bug report didn't have anything to do with disk full (on /boot). I assume at least and from memory. I would have noticed as I reinstalled kernel stull if I recall. Out of space happened later, see other comments and didn't really pose a problem, just some extra questions.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440811] Re: ibus-ui-gtk3 crashed with SIGABRT
See: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1235567 Probably same bug. Not sure if each version of Ubuntu should have each own bug (here or in general). This could (in theory) be a different bug (or the same..). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440811 Title: ibus-ui-gtk3 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1440811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441891] Re: Can't login after upgrade to 15.04 on Dell Inspiron 1525
I upgraded linux kernel (e.g. image) to 3.19.0.13.13 (versions in synaptic says (vivid), I may have assumed -proposed wrongly). Then I could log in (without older non-vivid kernel). I would close this bug if I knew for sure those who download get now the above kernel, not what I got first, 3.19.0.13.12. Otherwise, this might have to go into release notes. Probably the latest minor versions ends up in the release version, I just wander about those who download the beta, is that stuck in the past or is it a daily version? linux-header-generic still says 3.19.0.13.12. Doesn't seem to be a problem, it depends on stuff that has minor version number upgraded.. ** Description changed: - Below was fixed in -proposed, see first comment. + Below was fixed in an upgrade, please see first comment before closing + (I'm also trying to learn stuff and warn others..) [ubuntu-release-upgrader is probably the wrong package.. standing for 15.04 not working, not sure what to pin this on.. or what more info needed.] What I know for a fact: I did do-release-upgrade to upgrade to 15.04 (in fact twice, first to 14.10) After reboot to 15.04 I got the login-screen and the mouse pointer was frozen dead center. I can't type in the password go to virtual console or toggle CAPS LOCK light. However I could reboot and choose an old kernel and got a working WiFi. I tried (purging to force download and) reinstalling of bcmwl-kernel- source as: $ lspci |grep BCM 0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) It didn't help (in fact I lost WiFi in older kernels but fixed that..). Hardware drivers shows the above and: Unknown:Unknown Using Processor microcode firmware for Intel CPUs from intel-microcode (proprietary) [That is new, I hadn't seen before and it was disabled. Now enabled and doesn't make a difference. And not Intel should be upper case..] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.13 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Apr 8 22:02:35 2015 InstallationDate: Installed on 2014-08-21 (230 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-04-06 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441891] Re: Can't login after upgrade to 15.04 on Dell Inspiron 1525
** Description changed: + Below was fixed in -proposed, see first comment. + [ubuntu-release-upgrader is probably the wrong package.. standing for 15.04 not working, not sure what to pin this on.. or what more info needed.] What I know for a fact: I did do-release-upgrade to upgrade to 15.04 (in fact twice, first to 14.10) After reboot to 15.04 I got the login-screen and the mouse pointer was frozen dead center. I can't type in the password go to virtual console or toggle CAPS LOCK light. However I could reboot and choose an old kernel and got a working WiFi. I tried (purging to force download and) reinstalling of bcmwl-kernel- source as: $ lspci |grep BCM 0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) - It didn't help (in fact I lost WiFi in older kernels but fixed that..). - Hardware drivers shows the above and: Unknown:Unknown Using Processor microcode firmware for Intel CPUs from intel-microcode (proprietary) [That is new, I hadn't seen before and it was disabled. Now enabled and doesn't make a difference. And not Intel should be upper case..] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.13 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Apr 8 22:02:35 2015 InstallationDate: Installed on 2014-08-21 (230 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-04-06 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1441891] [NEW] Can't login after upgrade to 15.04 on Dell Inspiron 1525
Public bug reported: [ubuntu-release-upgrader is probably the wrong package.. standing for 15.04 not working, not sure what to pin this on.. or what more info needed.] What I know for a fact: I did do-release-upgrade to upgrade to 15.04 (in fact twice, first to 14.10) After reboot to 15.04 I got the login-screen and the mouse pointer was frozen dead center. I can't type in the password go to virtual console or toggle CAPS LOCK light. However I could reboot and choose an old kernel and got a working WiFi. I tried (purging to force download and) reinstalling of bcmwl-kernel- source as: $ lspci |grep BCM 0b:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01) It didn't help (in fact I lost WiFi in older kernels but fixed that..). Hardware drivers shows the above and: Unknown:Unknown Using Processor microcode firmware for Intel CPUs from intel-microcode (proprietary) [That is new, I hadn't seen before and it was disabled. Now enabled and doesn't make a difference. And not Intel should be upper case..] ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-release-upgrader-core 1:15.04.13 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Apr 8 22:02:35 2015 InstallationDate: Installed on 2014-08-21 (230 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to vivid on 2015-04-06 (2 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1441891 Title: Can't login after upgrade to 15.04 on Dell Inspiron 1525 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1441891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440811] [NEW] ibus-ui-gtk3 crashed with SIGABRT
Public bug reported: I'm getting this in 15.04: The application Keyboard Input Methods has closed unexpectedly. /usr/lib/ibus/ibus-ui-gtk3 There were other reports, but none for 15.04 it seemed so I reported again.. One special case: [This program doesn't seem essential to me (for Icelandic language) and probably should work in any kernel?] After installing 15.04 I can't actually boot in and do anything w/13.19. That is, I do not get far enough to get the above error. I have to start with an older kernel: $ uname -a Linux Ryksugan 3.16.0-34-generic #45-Ubuntu SMP Mon Mar 23 17:21:27 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux I may report another bug for the kernel problem.. I never got this in 14.04. Upgraded to 14.10 (to get to 15.04, didn't seem to be another way to it) where I got this error (from memory, exactly the same..) and then soon after to 15.04. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 6 16:56:09 2015 Disassembly: = 0x7f59dfc33267: Cannot access memory at address 0x7f59dfc33267 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2014-08-21 (227 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT UpgradeStatus: Upgraded to vivid on 2015-04-06 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash apport-failed-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440811 Title: ibus-ui-gtk3 crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1440811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
It's a dfferrent new bug. I think there is already a similar bug open. What languages are you using? Please try to unlock after changing the language in the keyboard indicator. I use Icelandic. It has extra letters, such as þæðöÞÆÐÖ (and accented), over English (as it is a superset I never change to English layout) but as I said I'm not using those in my password. And this bug had just happened for the first time while getting no password prompt has happened many times. I changed to gnome-shell, at least to try out, so I do not expect the bug to happen there.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Do you have multiple keyboard layouts? Yes, BUT I think you are getting at that with my layout the password would change if I press the same keys in another layout. It doesn't (matter if the English one is used). It's a guess. You think this could be adifferent manifestation if the same bug? Should *I* file a new one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I had a new development.. Maybe I should report as a new bug? In case this helps anyone as a workaround or to fix the bug I thought I would post here: I had the lock screen complain of the wrong password. I sure it was the right one as I tried many times and eventually opened a virtual terminal where the password worked (tried several times again in the lockscreen to be sure) BUT instead of using the unity or compiz trick as usual I found this process with ps -ef: /usr/lib/unity/unity-panel-service --lockscreen-mode and killed it, then the lock screen would take the password. This might be something for you to try I guess as as a workaround next time.. At least when I restarted the old way, the desktop, that is the panel, didn't quite work afterwards (at least the time disappears from the panel), and I would restart after getting in to be on the safe side. I might do that now also, but at least I do not seem to have any problems. [This may not stricly be the same bug, but I guess the bug is in the same program and I would guess both this and the bug in the subject have the same root cause - memory at some point running out and making trouble afterwards.] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1] Re: Microsoft has a majority market share
Shuttleworth may have closed this bug prematurely (haven't followed all comments..) based on iOS plus Android having majority over Windows. Anyway not important now as Android alone seems bigger than Windows now (including iOS and OS X etc - all others). @mwildam: although most people I know do have a smartphone (or two - a private one and a business phone) and maybe also have a tablet, ALL OF THEM do their main computer work with a PC or laptop. You cannot assume that most of the serious computer work is done from an Android phone or tablet. Why is that? And not sure it's true for all. For the global perspective most people probably do not have a PC while they may have a smartphone. You could say they only surf the web.. Programming for Android is even somewhat possible within the OS. Keyboard (and mouse) can be connected. QT works for Android and I wander how difficult it is to port most Linux programs to Android. My post on Ubuntu Touch to the mailing-list being a dead-end and Android compatibility being essentioal didn't make it there.. In 2013, Android-based devices outsold Windows' 2.8:1 (2:1 in mature markets) or by 573 million units (estimating the gap to widen much in 2014 and 2015). In India and other countries Android is the most popular operating system including for browsing the web; according to Statcounter; Mobile usage has already overtaken desktop in several countries including India, South Africa and Saudi Arabia[226] with several countries in Africa having done so already, including Ethiopia and Kenia (there mobile is 72.23%) See also: http://www.thedrum.com/news/2014/10/22/twitter-ceo-costolo- launches-free-mobile-development-kit-fabric-unite-developers-and -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1 Title: Microsoft has a majority market share To manage notifications about this bug go to: https://bugs.launchpad.net/clubdistro/+bug/1/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378919] Re: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug
This might be a different bug but I highly doubt it as the original bug behaviour followed: In the dash (right? When pressing Win-start) all icons suddenly stopped appearing. What had happened just before: I closed firefox (that had gotten slow) and updated firefox and more: 2014-10-16 14:30:47 upgrade firefox:amd64 34.0~b1+build1-0ubuntu0.14.04.1~ricotz1 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:52 upgrade firefox-locale-en:amd64 34.0~b1+build1-0ubuntu0.14.04.1~ricotz1 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:54 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 14:30:54 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16 14:30:55 status installed desktop-file-utils:amd64 0.22-1ubuntu1 2014-10-16 14:30:55 status installed bamfdaemon:amd64 0.5.1+14.04.20140409-0ubuntu1 2014-10-16 14:30:56 status installed mime-support:all 3.54ubuntu1 2014-10-16 14:30:59 status installed firefox:amd64 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 2014-10-16 14:30:59 status installed firefox-locale-en:amd64 34.0~b1+build2-0ubuntu0.14.04.1~ricotz1 Note the icons did not appear afterwards even though firefox was not running - memory may mave been limitted before when firefox was running but should have freed up when I closed it; nothing much else was running so it should not - still - be a problem in the dash. That is, it should not have happened, but in case it did, should have recovered. [I highly doubt the firefox update or others have anything to do with the icons gone as everything worked after a restart.] just preceded but is probably really just a coincidence except may have eaten up memory Then I reopened (the just updated) firefox that worked fine and had to lock the screen. There it was again, no entry field for the password. All was well after a restart before updating anything more. And also after fully updating (I believe these should have prevented the bug if installed according to their changelogs): 2014-10-16 15:08:29 upgrade thunderbird:amd64 1:31.1.2+build1-0ubuntu0.14.04.1 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:08:33 upgrade thunderbird-gnome-support:amd64 1:31.1.2+build1-0ubuntu0.14.04.1 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:17:15 upgrade bash:amd64 4.3-7ubuntu1.4 4.3-7ubuntu1.5 2014-10-16 15:17:19 upgrade libgl1-mesa-dri:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:21 upgrade libgbm1:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:21 upgrade libgles2-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:22 upgrade libgl1-mesa-glx:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:23 upgrade libwayland-egl1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:23 upgrade libegl1-mesa-drivers:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:24 upgrade libglapi-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:25 upgrade libopenvg1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:26 upgrade libegl1-mesa:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:27 upgrade libvncserver0:amd64 0.9.9+dfsg-1ubuntu1 0.9.9+dfsg-1ubuntu1.1 2014-10-16 15:17:27 upgrade libxatracker2:amd64 10.1.3-0ubuntu0.1 10.1.3-0ubuntu0.2 2014-10-16 15:17:31 upgrade gnome-calculator:amd64 1:3.10.2-0ubuntu1.1 1:3.10.2-0ubuntu1.2 2014-10-16 15:17:41 upgrade linux-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:42 upgrade linux-image-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:53 upgrade linux-headers-generic:amd64 3.13.0.37.44 3.13.0.38.45 2014-10-16 15:17:53 upgrade linux-libc-dev:amd64 3.13.0-37.64 3.13.0-38.65 2014-10-16 15:17:55 upgrade python3-requests:all 2.2.1-1 2.2.1-1ubuntu0.1 2014-10-16 15:17:55 upgrade liboxideqt-qmlplugin:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:17:56 upgrade liboxideqtcore0:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:18:00 upgrade oxideqt-codecs:amd64 1.0.5-0ubuntu0.14.04.1 1.2.5-0ubuntu0.14.04.1 2014-10-16 15:08:34 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16 15:08:34 status installed desktop-file-utils:amd64 0.22-1ubuntu1 2014-10-16 15:08:34 status installed bamfdaemon:amd64 0.5.1+14.04.20140409-0ubuntu1 2014-10-16 15:08:35 status installed mime-support:all 3.54ubuntu1 2014-10-16 15:08:36 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:08:37 status installed thunderbird:amd64 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:08:37 status installed thunderbird-gnome-support:amd64 1:31.2.0+build2-0ubuntu0.14.04.1 2014-10-16 15:17:17 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:17:17 status installed install-info:amd64 5.2.0.dfsg.1-2 2014-10-16 15:17:18 status installed bash:amd64 4.3-7ubuntu1.5 2014-10-16 15:18:01 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 2014-10-16 15:18:01 status installed man-db:amd64 2.6.7.1-1ubuntu1 2014-10-16 15:18:01 status installed gnome-menus:amd64 3.10.1-0ubuntu2 2014-10-16
[Bug 1378919] Re: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug
I'm not even sure if the lock-screen and dash are the same program (unity?), in case they are different and I just happened to trigger two bugs at once then memory being low (or low in the past) very probably is the common cause. I do not care too much about the dash (file bug separatly?) but the lockscreen is a critical one. I do not know how to flag is as such. ** Summary changed: - After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug + After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378919 Title: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug (and icons can go missing in dash) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378919] Re: After going to lock screen can't login as not prompted for password - maybe not a unity bug
Possibly suggesting this was memory related (not what follows is after restart): As I said AFTER restarting Unity I couldn't switch between windows (or so I thought). ALT-TAB didn't pop up the switcher. I later discovered that I the keybord shortcuts to switch seemed to work, just didn't see what I was doing. Then after initiating quit in Firefox and while it was shutting down (I guess it was slowly freeing up memory) I COULD switch WITH the graphics and see e.g. my Firefox windows and in the end one and one of them disappearing. CTRL-ALT-T to start terminal didn't however work - even afterwards and the panel was there with no info on the right or way to reboot. I had to use the virtual console. I would say this bug is critical for users - to possibly get locked out and - even with a workaround most would not know - not be able to recover. Note, if the box to input password doesn't appear because memory is low, one possibility would be to try to allocate enough memory before locking the screen. That could however be dangourous and change this bug into a security one if done wrong. If memory runs out BEFORE locking, what would happen? Would the screen then not lock? ** Summary changed: - After going to lock screen can't login as not prompted for password - maybe not a unity bug + After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378919 Title: After going to lock screen - sometimes can't log back in as not prompted for password - maybe not a unity bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378919] [NEW] After going to lock screen can't login as not prompted for password - maybe not a unity bug
Public bug reported: Expected: Under my name on login screen I should see the field to put in my password. [I took a picture, but probably not to helpful?] [Just a guess, could it be malloc not returning memory if memory tight?] uptime 16:12:36 up 9 days I update all that matters when I reset. At least unity: 2014-09-29 08:19:43 status installed unity:amd64 7.2.3+14.04.20140826-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:09 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-26 13:50:10 status installed libglib2.0-bin:amd64 2.40.2-0ubuntu1 /var/log/dpkg.log.1:2014-09-29 08:19:42 status installed libglib2.0-0:amd64 2.40.2-0ubuntu1 There are exections that I do not think matters: See: https://bugs.launchpad.net/unity/+bug/1378879 for bug that I manually submitted. [Then I couldn't run ubuntu-bug unity after pressing Win-start button. I still haven't reset machine and still can't but noticed I could from a shell.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Oct 8 16:00:40 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed bbswitch, 0.7, 3.13.0-37-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-36-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-37-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108GL [Quadro 600] [10de:0df8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0835] InstallationDate: Installed on 2014-08-26 (43 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Dell Inc. Precision T1650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=b342558f-2de5-4795-857d-67d51db3a726 ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0X9M3X dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/31/2013:svnDellInc.:pnPrecisionT1650:pvr01:rvnDellInc.:rn0X9M3X:rvrA04:cvnDellInc.:ct6:cvr: dmi.product.name: Precision T1650 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Sep 29 08:35:11 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 package-from-proposed trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378919 Title: After going to lock screen can't login as not prompted for password - maybe not a unity bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378919] Re: After going to lock screen can't login as not prompted for password - maybe not a unity bug
I'm not sure what all the auto-generated info is telling - supposedly should be saying what I was running and what config when I hit the bug. I assume however it's really telling what I'm runnig at bug-submit? I may have installed libraries but not restarted and then still using older libraries? Note I think that doesn't apply to unity but not sure what unity/compiz used directly or indirectly. Anyway I restarted recently and it's either a current bug or one fixed in last 9 days and can't see that from changelogs of stuff I haven't installed. Can't see changelog (in update-manager) for stuff I've installed after reset of machine but may not have been running when hitting the bug. Note what I said (including in previous bug submittion) that I restarted unity (and compiz) after the bug and before ubuntu-bug unity. I have several packages with this version and that version available (all with this changelog): Changes for libgbm1 versions: Installed version: 10.1.3-0ubuntu0.1 Available version: 10.1.3-0ubuntu0.2 Version 10.1.3-0ubuntu0.2: [ Timo Aaltonen ] * Drop fix-kwin.diff hack, as 10.1.3 has 0380ec467d78f40 which fixes the issue properly. [ Maarten Lankhorst ] * Add fix-svga-ioctl.patch (LP: #1365490) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378919 Title: After going to lock screen can't login as not prompted for password - maybe not a unity bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315918] Re: No sound played
Hi Kurt, I have both gawk and mawk installed. What were you trying to do? That is, in what application didn't you get a sound? If you had gawk installed for sure at the time, then your problem is not a duplicate of the musecore bug. I'm told that bug is not in pulseaudo (I'm not convinced, and will investigate and report only in that bug). Could it be that you didn't have gawk installed (it is not included by default in 14.04 and neither *I think* in 13.10) and you installed something that brought that package in (not always obvious) and then your sound-program started working, whether it was musescore or something else? Note gawk doesn't really have anything to do with sound on it's own and sound works out-of-the-box in 14.04 in all installed applications I assume. The other bug just proves that a missing gawk AND installing aprogram (eg. musescore) can disable it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315918 Title: No sound played To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1315918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
** Description changed: - xubuntu 14.04 - From http://musescore.org/en/node/22727 By default Ubuntu has mawk installed instead of gawk and so Musescore suspends pulseaudio when it does not need to. A temporary fix is to install gawk, however this should work out of the box. I've created a symlink to mawk and this seems to work, pulseaudio is not suspended anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
This failure is in Ubuntu 14.04 (and Xubuntu, I took that out from main bug description). I also have 13.10 that didn't have gawk (only mawk) installed. When installing musescore gawk got installed. Why would that not happen in 14.04? I guess there is a dependency missing but why all of a sudden? Should it be added or mawk be used? And why is there not a symlink then from gawk to (m)awk? And isn't that a more general but not just affecting musescore? And why should this disable sound in other programs - possibly (I'm not sure my second hand info is correct): http://musescore.org/node/22313 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
What I confirmed myself is I did not get a sound from this program and the time does not advance on the player. After closing the program sound was ok in other programs. I didn't try at the same time, but my brother says all sound was gone. He thought this program had broken all sound in the system (but would probably be ok if he had just closed the program). I'm not sure how I escalate, it looks bad (for LTS), say critical (non- security) bug, somehow? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
Assuming pulsuaudio gets disabled by musescore (I assume when you try to start playing, not when installing). That is assuming similiar to in link in comment #1. pulseaudio or audio in general is a core component of Ubuntu and shouldn't the bug be marked Critical (or at least Important)? Can anyone do that? ** Package changed: musescore (Ubuntu) = pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
** Package changed: pulseaudio (Ubuntu) = musescore (Ubuntu) ** Also affects: pulseaudio Importance: Undecided Status: New ** Also affects: pulseaudio (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/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315918] Re: No sound played
I wander if this bug is related to (can I provide wikilink between..?): https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1284273 I'm not saying they are duplicates or confirming this one. I'm a little new to this (sound problems). Did you have no sound straight after upgrading from 13.10? Is that it or maybe something in between as installing some program, musescore or otherwise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315918 Title: No sound played To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1315918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315918] Re: No sound played
I wanser if this bug is related to (can I provide wikilink between..?): https://bugs.launchpad.net/ubuntu/+source/musescore/+bug/1284273 I'm not saying they are duplicates or confirming this one. I'm a little new to this (sound problems). Did you have no sound straight after upgrading from 13.10? Is that it or maybe something in between as installing some program, musescore or otherwise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315918 Title: No sound played To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1315918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
I confirmed the bug for musescore, not 100% sure pulseaudio is the problem, just trusting suspends pulseaudio from bug-title and seems similar to link I provided in #1. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed ** Description changed: + [Páll confirmed musescore, and added pulseaudio and confirmed that + (99% sure).] + From http://musescore.org/en/node/22727 By default Ubuntu has mawk installed instead of gawk and so Musescore suspends pulseaudio when it does not need to. A temporary fix is to install gawk, however this should work out of the box. I've created a symlink to mawk and this seems to work, pulseaudio is not suspended anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1284273] Re: Musescore mistakenly suspends pulseaudio because of missing gawk
** Description changed: [Páll confirmed musescore, and added pulseaudio and confirmed that - (99% sure).] + (99% sure). Not sure if PulseAudio (upstream), I added, should + included/needed/confirmed or/and pusleaudio (Ubuntu) only.] From http://musescore.org/en/node/22727 By default Ubuntu has mawk installed instead of gawk and so Musescore suspends pulseaudio when it does not need to. A temporary fix is to install gawk, however this should work out of the box. I've created a symlink to mawk and this seems to work, pulseaudio is not suspended anymore ** Description changed: [Páll confirmed musescore, and added pulseaudio and confirmed that (99% sure). Not sure if PulseAudio (upstream), I added, should - included/needed/confirmed or/and pusleaudio (Ubuntu) only.] + included/needed/confirmed or/and pulseaudio (Ubuntu) only.] From http://musescore.org/en/node/22727 By default Ubuntu has mawk installed instead of gawk and so Musescore suspends pulseaudio when it does not need to. A temporary fix is to install gawk, however this should work out of the box. I've created a symlink to mawk and this seems to work, pulseaudio is not suspended anymore ** Description changed: [Páll confirmed musescore, and added pulseaudio and confirmed that - (99% sure). Not sure if PulseAudio (upstream), I added, should + (99% sure). Not sure if PulseAudio (upstream), I added, should included/needed/confirmed or/and pulseaudio (Ubuntu) only.] From http://musescore.org/en/node/22727 By default Ubuntu has mawk installed instead of gawk and so Musescore suspends pulseaudio when it does not need to. A temporary fix is to install gawk, however this should work out of the box. I've created a symlink to mawk and this seems to work, pulseaudio is not suspended anymore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284273 Title: Musescore mistakenly suspends pulseaudio because of missing gawk To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1284273/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292707] [NEW] gcalctool (or its libraries?) seems to have a memory leak
Public bug reported: I assume there is a memory leak as the old gcalctool process uses 1704 MB? Correct? Just started a new one and can't see that one with top, that far down the list. Note I haven't been doing anything complicated with the calculator, just some simple additions. May have done multiplications but not divisions or more complicated, if I recall. Probably not whole numbers all of them but not very big numbers if it matters. [I was willing to do a coredump if something like that is needed. Does ubuntu-bug do that? If not, would it be helpful? In general does it collect all relevant info? Non-standard info/kernels/config? I have 3.11.0-17-generic running with some -proposed but mostly standard stuff. See at bottom (shouldn't/couldn't ubuntu-bug provide this?). I might delay killing it for a while unless I hear something.] ps -ef |grep gcalctool palli 9951 1 0 19:57 ?00:00:00 gcalctool palli24874 1 0 Feb13 ?00:01:09 gcalctool Mem: 4037780k total, 3814604k used, 223176k free, 4284k buffers Swap: 8377336k total, 3469388k used, 4907948k free, 713860k cached Sorted by VIRT: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 23529 palli 20 0 4357m 2.5g 11m R 92 63.8 235:03.13 firefox 4065 palli 20 0 1704m 55m 8060 R 16 1.4 519:57.55 compiz 24874 palli 20 0 1278m 7760 1312 S0 0.2 1:09.40 gcalctool 23090 palli 20 0 1096m 8936 1352 S0 0.2 2:36.01 update-manager 4087 palli 20 0 1048m 2828 324 S0 0.1 0:39.67 nautilus 2164 root 20 0 1020m 44 44 S0 0.0 0:24.17 console-kit-dae 1838 root 20 0 1016m 53m 1704 S 28 1.4 493:50.98 Xorg 4059 palli 20 0 949m 2824 624 S0 0.1 2:27.35 gnome-settings- Unrelated blable per se: Not too worried about gcalctool, you could call it an introductory bug from me. Just learning the ropes and getting a handle on things so I can submit a bug on the big one: I was debugging a memory issue (Firefox), and was just amazed that the calculator would be the third biggest program (above Xorg!). I'm not to worried as RES should(?) affect me the most (and maybe SHR?) but VIRT is mostly on disk. However, note that I use zram and how big the swap is, not sure if it is a wise choice. update-manager seems also to be a huge memory/cpu/network-hog (know the program is changed in 13.10). Also a memory leak or just a memory-hog? Sorted by RES (a little later): 23529 palli 20 0 4110m 2.2g 12m R 93 57.4 293:43.87 firefox 1838 root 20 0 1012m 53m 1828 R 54 1.3 520:38.40 Xorg 4065 palli 20 0 1695m 52m 6488 R9 1.3 525:25.36 compiz 4160 palli 20 0 650m 23m 3412 S0 0.6 4:43.98 unity-panel-ser 27130 root 20 0 25920 15m 14m S0 0.4 0:00.01 memlockd 9951 palli 20 0 508m 11m 4840 S0 0.3 0:01.32 gcalctool 19476 palli 20 0 630m 10m 3840 S2 0.3 6:43.58 gnome-terminal 4309 palli 20 0 247m 9272 176 S0 0.2 0:06.21 zeitgeist-fts 4159 palli 20 0 685m 9232 1288 S0 0.2 2:59.51 hud-service 23090 palli 20 0 1096m 8412 800 S0 0.2 2:36.17 update-manager 24040 palli 20 0 551m 7720 2504 S8 0.2 36:24.58 gnome-system-mo Note how firefox shrank (didn't close anything) and how updatem-manager changes. Assume the numbers for these processes are normal. I'm assuming newly installed memlockd is not a factor in any of this. Stopped and started
[Bug 1212659] [NEW] package postgres-xc 1.0.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: There was an error when I installed with synaptic, but if I remember correctly this bug reporting thing started when I tried to uninstall (was forced to when installing client for regular postgresql that seemd to conflict). I got some broken packages in this process but not to sure if that matters (or to familiar with broken packages to fix). ProblemType: Package DistroRelease: Ubuntu 13.10 Package: postgres-xc 1.0.3-1 ProcVersionSignature: Ubuntu 3.10.0-5.14-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Thu Aug 15 11:36:19 2013 DuplicateSignature: package:postgres-xc:1.0.3-1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-08-01 (13 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130726) MarkForUpload: True SourcePackage: postgres-xc Title: package postgres-xc 1.0.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postgres-xc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212659 Title: package postgres-xc 1.0.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgres-xc/+bug/1212659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769874] Re: Naming restrictions in UFL considered non-free by Debian
I listet bug #1167425 as duplicate of this one and then took it back. I was probaly to hasty since it was intentionally filed separately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769874 Title: Naming restrictions in UFL considered non-free by Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-font-family/+bug/769874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116801] Re: About section of system settings reports wrong version of Ubuntu (12.04.1)
** Summary changed: - About section of sytem settings reports wrong version of Ubuntu (12.04.1) + About section of system settings reports wrong version of Ubuntu (12.04.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116801 Title: About section of system settings reports wrong version of Ubuntu (12.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1116801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 937815] Re: gtk-window-decorator crashed with SIGSEGV in max_window_name_width()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/937815 Title: gtk-window-decorator crashed with SIGSEGV in max_window_name_width() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/937815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
