[Bug 1954598] [NEW] gcc ignores large _Alignas specifiers on static .bss data
Public bug reported:
Instructions to reproduce: compile the following C program:
```
#include
static _Alignas(4 << 20) int x;
int main(void) {
printf("%#llx\n", (long long) );
return 0;
}
```
using `gcc` with no arguments other than the program's filename (which
must end `.c` so that gcc interprets it as a C program), and run the
resulting a.out.
Expected behaviour: the program prints a number that's divisible by 2²²
(in hexadecimal, the resulting number will end with five zeroes, and the
preceding digit will be divisible by 4).
Actual behaviour: the program prints an arbitrary number that's
divisible by 2¹², but which is normally not divisible by 2²². (The exact
number varies between runs of the program; some example observed values
include 0x55c2be889000 and 0x55d2cd348000.)
This bug seems to be somehow specific to the way Ubuntu has configured
`gcc` – it doesn't show up on a Red Hat-based Linux system, or when
compiling using `clang`. As far as I can tell, the bug isn't in the
compiler portion of `gcc`, but rather in the driver process; something
in the arguments that it's passing to the linker is causing this
behaviour.
I suspect that the bug is related to position independent code. (In
particular, compiling with `gcc -fno-pie` will cause an error along the
line of `/usr/bin/ld: /tmp/cc6nztmN.o: relocation R_X86_64_32 against
`.bss' can not be used when making a PIE object; recompile with -fPIE`,
rather than linking successfully, which means that the linker has been
told by the compiler to make a position-independent executable even when
the user explicitly tells it not to.)
It is possible that this misbehaviour has been introduced intentionally
for security reasons (because requiring a large alignment for the
program image reduces the amount of security that address space layout
randomization can provide). However, in this case, I think the correct
behaviour should be to reject the program with an error, rather than
apparently compiling it successfully, but producing a program that gives
incorrect results at runtime.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gcc 4:9.3.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
Date: Sun Dec 12 17:01:45 2021
InstallationDate: Installed on 2019-11-11 (761 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
SourcePackage: gcc-defaults
UpgradeStatus: Upgraded to focal on 2020-10-02 (436 days ago)
** Affects: gcc-defaults (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954598
Title:
gcc ignores large _Alignas specifiers on static .bss data
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1954598/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
I can no longer reproduce this bug. I assume it got fixed at some point, either intentionally or as a side effect of some other upstream change. Marking it as invalid – I assume that's the right status for bugs that can no longer be reproduced? ** Changed in: linux (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946197] [NEW] gprolog builtin phrase/3 incorrectly succeeds when matching constant lists
Public bug reported: gprolog seems to be producing incorrect results when using the phrase/3 builtin. In particular, the symptom is that when phrase/3 is used to match a DCG that requires its input to start with a particular string/list, and the input actually starts with something else, phrase/3 reports that there was a match (returning an unbound list for the remaining unconsumed input), rather than reporting that there was no match. Example to reproduce: start gprolog, and give it the input line phrase([2], [1,2], T). Expected behaviour: gprolog answers "no": this query is equivalent to "remove the prefix [2] from the list [1,2] and bind the remainder to T", and [1,2] does not start with [2], so this task should be impossible. I've verified that this is the expected/correct output against both gprolog's documentation, and against swipl (a different Prolog implementation). Actual behaviour: gprolog answers "yes", without binding anything to T (it remains an unbound variable). The problem seems to be specific to the case of there being no match; with the comparable phrase([1], [1,2], T). gprolog will produce the output of "T=[2]" and "yes" (the expected output), and will not suggest a second solution with T unbound. It's also specific to the use of phrase/3 for evaluating DCG literals directly; using the --> operator to give a name to the grammar consisting only of [2], then executing that grammar (whether directly or with phrase/3), produces the correct results. phrase/2 seems to have the same buggy behaviour as phrase/3 (probably because it's implemented as calling phrase/3 behind the scenes). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gprolog 1.4.5.0-3 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Oct 6 08:42:51 2021 ExecutablePath: /usr/lib/gprolog/bin/gprolog InstallationDate: Installed on 2019-11-11 (694 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: gprolog UpgradeStatus: Upgraded to focal on 2020-10-02 (368 days ago) ** Affects: gprolog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946197 Title: gprolog builtin phrase/3 incorrectly succeeds when matching constant lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gprolog/+bug/1946197/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629587] Re: ESC ] 6; 12; ? ESC \ freezes xterm with 100% CPU usage
** Changed in: xterm (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629587 Title: ESC ] 6;12;? ESC \ freezes xterm with 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1629587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened
I can confirm that the bug described in the askubuntu.com link above is the bug I'm seeing; the workaround stated there (renaming `~/.fonts`) was enough to prevent it occurring. I have fontconfig 2.12.6-0ubuntu2 installed (and my fontconfig-config is the same version). Should this bug report be moved to the fontconfig package, as apparently it's the underlying cause of the bug? Presumably it will be fixed if/when Ubuntu updates to a newer version of fontconfig. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856624 Title: Firefox freezes temporarily at 100% CPU when Chromium is opened To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1856624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened
I have a total of 8 GB of RAM and 2 GB of swap. Reproducing the issue with a memory monitor opened, however, showed that the issue was not related to memory exhaustion: I had at least 2 GB of unused RAM at all times, and although the swap was enabled, it was not used (the swap usage remained at 0 throughout the entire period). Also observed during this test: eight Firefox processes (seven Web Content and one WebExtensions) were running at 50% CPU usage each throughout the time of nonresponsiveness (my computer has 4 cores, so between them they were using up the entire CPU usage of the computer). ** Changed in: firefox (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856624 Title: Firefox freezes temporarily at 100% CPU when Chromium is opened To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814529] Re: apport-bug does nothing after choosing the "Send" option
Although it was reliably reproducable at the time, I can no longer reproduce this bug (using ubuntu-bug version 2.20.9 on Ubuntu Bionic). Perhaps it's been fixed incidentally. ** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814529 Title: apport-bug does nothing after choosing the "Send" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856624] [NEW] Firefox freezes temporarily at 100% CPU when Chromium is opened
Public bug reported:
When Firefox is open, and I open Chromium, many features of Firefox fail
to work for several seconds. (To reproduce, start with neither Firefox
nor Chromium open; open Firefox, and allow one or more web pages to
load; then open Chromium; the issue starts a second or two after
Chromium is opened.) This is a temporary issue, lasting for several
seconds; the length of time it lasts appears to depend on how many open
tabs have been viewed since Firefox opened (on my computer, around 10
seconds with 1 tab having been viewed, around a minute with 10 tabs
having been viewed). This reproduces even when running Firefox as
`firefox -safe-mode`.
While the issue is ongoing (i.e. starting around a second after Chromium is
open, and persisting for typically tens of seconds), some features of Firefox
work, but most do not:
- Scrolling the current tab short distances succeeds, showing the expected text
on the page.
- Scrolling the current tab long distances (several screeenfuls) causes the
page to be "cut off" past a certain point, with only a blank background
rendering.
- Moving the mouse cursor over a link does not change the mouse cursor
(expected behaviour, and behaviour while the issue is not ongoing, is for it to
change to a hand shape).
- Changing tab causes the resulting page not to display: rather, a grey
background is displayed, and sometimes a loading spinner.
- Changing tab back then causes the original page not to render, as if it were
new, despite the fact it was correctly displayed earlier.
- The address bar functions as normal; the issue does not appear to affect
address bar functionality.
Additionally, while the issue is ongoing, Firefox uses 100% CPU.
At some point after the issue in question starts, it stops, and all
Firefox features return to normal (including any missing or incorrectly
rendered page content, which renders again when the issue ends).
The trigger is specifically the act of opening Chromium: Firefox can
function just fine once the issue ends, even if Chromium is still open,
and functions just fine if Chromium is opened first.
I have an (unconfirmed) theory that opening Chromium is causing some
operation within Firefox to become very slow, using up all the CPU time,
and the other observed misbehaviours within Firefox are a consequence of
how slowly it is running; however, I've listed them all anyway in case
it provides clarity into what the specific nature of the bug is.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 71.0+build5-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ais523 1800 F pulseaudio
BuildID: 20191205184924
Channel: Unavailable
CurrentDesktop: X-Cinnamon
Date: Tue Dec 17 00:29:10 2019
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Français Language Pack - langpack...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-11-11 (35 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
IpRoute:
default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600
169.254.0.0/16 dev wlp2s0 scope link metric 1000
192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600
MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:722
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=71.0/20191205184924 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 0DDKKC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.5.1:bd05/30/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0DDKKC:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3583
dmi.product.sku: 08CA
dmi.sys.vendor: Dell Inc.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856624
Title:
Firefox freezes temporarily at 100% CPU whe
[Bug 1823708] Re: package xterm 330-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
>From your attached DpkgLog.txt: > 2019-04-02 17:26:52 status half-installed xterm:amd64 330-1ubuntu2 This isn't anything that xterm itself has control over. The half- installed status listed means that not all the files that are part of xterm have even been unpacked on your computer (presumably because you ran out of disk space mid-install). `dpkg` doesn't have enough information to be able to fix this, as it doesn't know where to look for the missing files that are part of xterm, and thus can't complete enough of the installation to be able to set up a running xterm installation. In order to fix this problem, you will need to use a program that can download the missing parts of xterm from a repository, such as `apt`. You could use a command like this to reinstall xterm, overwriting your broken xterm half-installation: > sudo apt install --reinstall xterm (This will fetch any missing parts of xterm from the Internet, meaning that they don't have to be present on your computer.) I'm marking this bug as invalid in xterm as there's really nothing that xterm can do about it: when parts of a program simply aren't there, it's basically impossible for the program to recover itself. You have to let the package manager do that for you. ** Changed in: xterm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823708 Title: package xterm 330-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1823708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814529] Re: apport-bug does nothing after choosing the "Send" option
It isn't (except that if apport-bug were working, it would have made sure the bug was filed against the right package!). Sorry, it's easy to make a mistake when filing a bug manually. ** Package changed: evolution (Ubuntu) => apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814529 Title: apport-bug does nothing after choosing the "Send" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814527] Re: "previous" button in Evolution's in-message search box finds the next match, not the previous match
Upstream have committed a fix at https://gitlab.gnome.org/GNOME/evolution/commit/b66cdbbe6f33bcbfc12af52b788cf87f7c78c40b. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814527 Title: "previous" button in Evolution's in-message search box finds the next match, not the previous match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1814527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814527] Re: "previous" button in Evolution's in-message search box finds the next match, not the previous match
Reported upstream as https://gitlab.gnome.org/GNOME/evolution/issues/318. (Launchpad thinks GNOME's bug tracker is somewhere else, so I haven't been able to link that bug report to this one "officially".) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814527 Title: "previous" button in Evolution's in-message search box finds the next match, not the previous match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1814527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814529] Re: apport-bug does nothing after choosing the "Send" option
`apport-cli --save /tmp/1814529.apport apport` appears to save the collected information to a file, as intended. I used this mechanism to generate the following information so that I could attach it to this bug report (due to this bug, I can't use the normal mechanism): ProblemType: Bug ApportLog: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Feb 4 12:06:04 2019 Dependencies: adduser 3.116ubuntu1 apport 2.20.9-0ubuntu7.5 apport-symptoms 0.20 apt 1.6.8 apt-utils 1.6.8 bzip2 1.0.6-8.1 ca-certificates 20180409 dbus 1.12.2-1ubuntu1 debconf 1.5.66 debconf-i18n 1.5.66 distro-info-data 0.37ubuntu0.2 dmsetup 2:1.02.145-4.1ubuntu3 dpkg 1.19.0.5ubuntu2.1 fdisk 2.31.1-0.4ubuntu3.3 file 1:5.32-2ubuntu0.1 gcc-8-base 8.2.0-1ubuntu2~18.04 gir1.2-glib-2.0 1.56.1-1 gpgv 2.2.4-1ubuntu1.2 init-system-helpers 1.51 iso-codes 3.79-1 libacl1 2.2.52-3build1 libapparmor1 2.12-4ubuntu5.1 libapt-inst2.0 1.6.8 libapt-pkg5.0 1.6.8 libargon2-0 0~20161029-1.1 libattr1 1:2.4.47-2build1 libaudit-common 1:2.8.2-1ubuntu1 libaudit1 1:2.8.2-1ubuntu1 libblkid1 2.31.1-0.4ubuntu3.3 libbz2-1.0 1.0.6-8.1 libc6 2.27-3ubuntu1 libcap-ng0 0.7.7-3.1 libcap2 1:2.25-1.2 libcryptsetup12 2:2.0.2-1ubuntu1.1 libdb5.3 5.3.28-13.1ubuntu1 libdbus-1-3 1.12.2-1ubuntu1 libdevmapper1.02.1 2:1.02.145-4.1ubuntu3 libexpat1 2.2.5-3 libfdisk1 2.31.1-0.4ubuntu3.3 libffi6 3.2.1-8 libgcc1 1:8.2.0-1ubuntu2~18.04 libgcrypt20 1.8.1-4ubuntu1.1 libgirepository-1.0-1 1.56.1-1 libglib2.0-0 2.56.3-0ubuntu0.18.04.1 libglib2.0-data 2.56.3-0ubuntu0.18.04.1 libgmp10 2:6.1.2+dfsg-2 libgnutls30 3.5.18-1ubuntu1 libgpg-error0 1.27-6 libgpm2 1.20.7-5 libhogweed4 3.4-1 libicu60 60.2-3ubuntu3 libidn11 1.33-2.1ubuntu1 libidn2-0 2.0.4-1.1build2 libip4tc0 1.6.1-2ubuntu2 libjson-c3 0.12.1-1.3 libkmod2 24-1ubuntu3.2 liblocale-gettext-perl 1.07-3build2 liblz4-1 0.0~r131-2ubuntu3 liblzma5 5.2.2-1.3 libmagic-mgc 1:5.32-2ubuntu0.1 libmagic1 1:5.32-2ubuntu0.1 libmount1 2.31.1-0.4ubuntu3.3 libmpdec2 2.4.2-1ubuntu1 libncurses5 6.1-1ubuntu1.18.04 libncursesw5 6.1-1ubuntu1.18.04 libnettle6 3.4-1 libp11-kit0 0.23.9-2 libpam-modules 1.1.8-3.6ubuntu2 libpam-modules-bin 1.1.8-3.6ubuntu2 libpam-runtime 1.1.8-3.6ubuntu2 libpam-systemd 237-3ubuntu10.11 libpam0g 1.1.8-3.6ubuntu2 libpcre3 2:8.39-9 libpolkit-agent-1-0 0.105-20ubuntu0.18.04.4 libpolkit-backend-1-0 0.105-20ubuntu0.18.04.4 libpolkit-gobject-1-0 0.105-20ubuntu0.18.04.4 libprocps6 2:3.3.12-3ubuntu1.1 libpython3-stdlib 3.6.7-1~18.04 libpython3.6-minimal 3.6.7-1~18.04 libpython3.6-stdlib 3.6.7-1~18.04 libreadline7 7.0-3 libseccomp2 2.3.1-2.1ubuntu4 libselinux1 2.7-2build2 libsemanage-common 2.7-2build2 libsemanage1 2.7-2build2 libsepol1 2.7-1 libsmartcols1 2.31.1-0.4ubuntu3.3 libsqlite3-0 3.22.0-1 libssl1.1 1.1.0g-2ubuntu4.3 libstdc++6 8.2.0-1ubuntu2~18.04 libsystemd0 237-3ubuntu10.11 libtasn1-6 4.13-2 libtext-charwidth-perl 0.04-7.1 libtext-iconv-perl 1.7-5build6 libtext-wrapi18n-perl 0.06-7.1 libtinfo5 6.1-1ubuntu1.18.04 libudev1 237-3ubuntu10.11 libunistring2 0.9.9-0ubuntu1 libuuid1 2.31.1-0.4ubuntu3.3 libxml2 2.9.4+dfsg1-6.1ubuntu1.2 libzstd1 1.3.3+dfsg-2ubuntu1 lsb-base 9.20170808ubuntu1 lsb-release 9.20170808ubuntu1 mime-support 3.60ubuntu1 mount 2.31.1-0.4ubuntu3.3 networkd-dispatcher 1.7-0ubuntu3.3 openssl 1.1.0g-2ubuntu4.3 passwd 1:4.5-1ubuntu1 perl-base 5.26.1-6ubuntu0.3 policykit-1 0.105-20ubuntu0.18.04.4 procps 2:3.3.12-3ubuntu1.1 psmisc 23.1-1ubuntu0.1 python-apt-common 1.6.3 python3 3.6.7-1~18.04 python3-apport 2.20.9-0ubuntu7.5 python3-apt 1.6.3 python3-certifi 2018.1.18-2 python3-chardet 3.0.4-1 python3-dbus 1.2.6-1 python3-gi 3.26.1-2 python3-httplib2 0.9.2+dfsg-1 python3-idna 2.6-1 python3-minimal 3.6.7-1~18.04 python3-pkg-resources 39.0.1-2 python3-problem-report 2.20.9-0ubuntu7.5 python3-requests 2.18.4-2ubuntu0.1 python3-requests-unixsocket 0.1.5-3 python3-six 1.11.0-2 python3-systemd 234-1build1 python3-urllib3 1.22-1 python3.6 3.6.7-1~18.04 python3.6-minimal 3.6.7-1~18.04 readline-common 7.0-3 shared-mime-info 1.9-2 systemd 237-3ubuntu10.11 tar 1.29b-2ubuntu0.1 ubuntu-keyring 2018.09.18.1~18.04.0 util-linux 2.31.1-0.4ubuntu3.3 uuid-runtime 2.31.1-0.4ubuntu3.3 xdg-user-dirs 0.17-1ubuntu1 xz-utils 5.2.2-1.3 zlib1g 1:1.2.11.dfsg-0ubuntu2 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-31 (733 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: apport 2.20.9-0ubuntu7.5 PackageArchitecture: all ProcCpuinfoMinimal: processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 142 model name : Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz stepping : 9 microcode : 0x8e cpu MHz: 2254.278 cache size : 3072 KB physical id: 0 siblings : 4 core id: 1 cpu cores : 2 apicid : 3
[Bug 1814529] Re: apport-bug does nothing after choosing the "Send" option
And an attempt using apport-collect:
I ran the command `apport-collect 1814529`.
apport-collect noticed the lack of authorisation, printing the following
text (I redacted the OAuth token):
{{{
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=«redacted»_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
}}}
The page in question did indeed open in my web browser. After I used
that page to authorise my computer, Apport opened the "collecting
information" and then "Send problem report to the developers?" dialog
boxes, as expected. However, when I then clicked "Send", apport-collect
exited with no visible further effect (and no messages on standard
output or standard error). Expected behaviour was to attach the
collected information to this bug report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814529
Title:
apport-bug does nothing after choosing the "Send" option
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1814529/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814529] [NEW] apport-bug does nothing after choosing the "Send" option
Public bug reported: After running apport-bug as, e.g., `apport-bug apport` (which I attempted to use to file this bug), it (as expected) puts up a dialog box specifying collected information, then shows that information with two options, "Send" and "Don't Send". However, clicking either button closes apport-bug with no visible further effect (and no messages on standard output or standard error). Expected behaviour is for apport-bug to open a page in my Web browser to allow me to file the bug. If I revoke my computer's authorisation at https://launchpad.net/~ais523 /+oauth-tokens and then repeat the process, there's no change to the observed behaviour (in particular, apport-bug doesn't ask for a new one). ** Affects: evolution (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/1814529 Title: apport-bug does nothing after choosing the "Send" option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1814529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814527] [NEW] "previous" button in Evolution's in-message search box finds the next match, not the previous match
Public bug reported: Steps to reproduce: In Evolution, open any email by double-clicking on it (so that the email appears in a separate window). Press Ctrl-Shift-F to bring up a search box at the bottom of the screen (allowing you to search for words in an email). Type in a word that appears at least three times in the email, and press Return, then start using the "Previous" and "Next" buttons next to it. Expected behaviour: the "Next" button jumps to the next occurrence of that word in the email; the "Previous" button jumps to the previous occurrence of that word in the email. Actual behaviour: the "Next" button acts as expected, but the "Previous" button acts identically to the "Next" button, moving to the next (rather than previous) occurrence of that word in the email. ** Affects: evolution (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/1814527 Title: "previous" button in Evolution's in-message search box finds the next match, not the previous match To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1814527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760907] Re: Netbeans 8.1 crash in splash screen
Re comment 2, I believe there are two bugs here, but this is the important one. People are seeing a crash accompanied by a warning about a Java 9 deprecation, and assuming they're connected, and thus are reporting the Java 9 deprecation (#1763091). However, the crash occurs even without the use of Java 9 (this bug), and in an identical way regardless of which version of Java is used. It's not clear what the most useful way to track this in the bug tracker would be. Marking them as duplicates would probably not be technically correct, but might be most useful for end users (who are likely to see the two bugs at the same time). At the very least, there should be clear pointers back and forth. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760907 Title: Netbeans 8.1 crash in splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1760907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760907] Re: Netbeans 8.1 crash in splash screen
Upstream bug report: https://issues.apache.org/jira/browse/NETBEANS-756?jql=project%20%3D%20NETBEANS%20AND%20text%20~%20crash (I can't link this to the Launchpad report the usual way because Netbeans has changed bug tracker, and Launchpad will only acknowledge the old tracker's URL.) Netbeans apparently consider this to not be a bug (!), on the basis that it expects some of its folders which are currently stored under /usr/share to be user-writable. Presumably, this is a packaging issue; if the software is going to assume that directories are user-writable we're going to have to move them to dotfiles or the like. It would help to get clarification on exactly which parts of the directory are meant to be writable; "all of it" would a) be horrible practice and b) make packaging it very difficult, because a large amount of fixed content is meant to be stored there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760907 Title: Netbeans 8.1 crash in splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1760907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763091] Re: netbeans fails to start due to java9
(By the way, should this bug be marked as a duplicate of #1760907? I assume most people who are subscribed to this care more about the crash than the use of a deprecated feature that still works. The crash has nothing to do with Java 9, though; it can be reproduced even running NetBeans under Java 8.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763091 Title: netbeans fails to start due to java9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1763091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763091] Re: netbeans fails to start due to java9
I believe that there are two separate bugs here. One is the deprecated reflective access. However, that isn't what's preventing NetBeans from loading; it's only a warning after all. I think the failure to load is a different bug. That's being discussed in #1760907. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763091 Title: netbeans fails to start due to java9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1763091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760907] Re: Netbeans 8.1 crash in splash screen
I've been looking into this bug myself (Launchpad's duplicate finder isn't suggesting this bug as a duplicate target so it's been reported several times by many people, including me). My findings are summarised in #1776724. Unfortunately I don't know what's causing it, but there might be enough information there to go on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760907 Title: Netbeans 8.1 crash in splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1760907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760907] Re: Netbeans 8.1 crash in splash screen
Although the original bug report was incomplete, there's more complete information at the duplicates. Marking as confirmed because the bug affects multiple users. ** Changed in: netbeans (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760907 Title: Netbeans 8.1 crash in splash screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1760907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775770] Re: netbeans runtime error
*** This bug is a duplicate of bug 1763091 *** https://bugs.launchpad.net/bugs/1763091 ** This bug has been marked a duplicate of bug 1763091 netbeans fails to start due to java9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775770 Title: netbeans runtime error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1775770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776724] Re: NetBeans crashes on startup
*** This bug is a duplicate of bug 1760907 *** https://bugs.launchpad.net/bugs/1760907 ** This bug has been marked a duplicate of bug 1760907 Netbeans 8.1 crash in splash screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776724 Title: NetBeans crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776724] Re: NetBeans crashes on startup
An Ask Ubuntu question that appears to be describing the same issue: https://askubuntu.com/questions/1036508/netbeans-8-1-wont-make-it-past- turning-on-modules-screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776724 Title: NetBeans crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776724] Re: NetBeans crashes on startup
I was wondering if there was something in my dotfiles which was causing the issue, so I tried again on a newly created user account. Unfortunately, that gave the same results as before. However, I did manage to locate where NetBeans was sending its error output (.netbeans/8.1/var/log/messages.log). The file in question appears to contain a stack backtrace, which may well help to solve the problem; I've attached it to this bug report. ** Attachment added: "Content of .netbeans/8.1/var/log/messages.log immediately after the crash on the newly created user account" https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+attachment/5152285/+files/messages.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776724 Title: NetBeans crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629587] Re: ESC ] 6; 12; ? ESC \ freezes xterm with 100% CPU usage
This is now fixed in Ubuntu Bionic. Version information: $ xterm -version XTerm(330) $ dpkg -s xterm | grep ^Version Version: 330-1ubuntu2 This seems consistent with the statement that it was fixed in version 326d. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629587 Title: ESC ] 6;12;? ESC \ freezes xterm with 100% CPU usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1629587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207000] Re: Maximus causes windows to stop painting
Confirmed that this still happens on Bionic. Given that Maximus is still on version 0.4.14-4, I guess that wasn't particularly surprising, but I decided to test anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207000 Title: Maximus causes windows to stop painting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maximus/+bug/1207000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776724] Re: NetBeans crashes on startup
The mention of the system tray made me think that it's possible the desktop environment was relevant, but I just tested and it isn't; I get the same behaviour on all of Cinnamon, MATE, and Ubuntu's version of Gnome 3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776724 Title: NetBeans crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776724] [NEW] NetBeans crashes on startup
Public bug reported:
When I load NetBeans (whether via the GUI or from a command line), the
splash screen appears and loads as far as "Turning on modules..."
(usually; very occasionally it gets stuck at "Reading module storage..."
instead). The splash screen then freezes for approximately 11-12 seconds
and then the entire program exits. Expected behaviour is that when I
load NetBeans, the loading process finishes and then the application's
main interface opens, without the process exiting.
I have two JREs installed, /usr/lib/jvm/java-8-openjdk-
amd64/jre/bin/java and /usr/lib/jvm/java-11-openjdk-amd64/bin/java. The
same behaviour of the splash screen occurs regardless of which JRE is
pointed at via "/usr/bin/java".
I also have two versions of javac installed, /usr/lib/jvm/java-8
-openjdk-amd64/bin/javac and /usr/lib/jvm/java-11-openjdk-
amd64/bin/javac. The choice of javac that "/usr/bin/javac" points to
does influence the results. I suspect that the difference is immaterial
but am mentioning it just in case:
* When using the Java 8 version of javac, no message is printed when NetBeans
exits this way; it simply exits to the command prompt (or the desktop if loaded
via the GUI) without printing anything. The exit status is 2.
* When using the "java-11-openjdk-amd64" version of javac (which claims to be
"javac 10.0.1" in its version info; thus I'm not clear on whether this is Java
10 or Java 11), the following messages are printed on standard output/error,
before it exits with exit status 2 (I suspect these are unrelated to the crash,
but including them just in case):
{{{
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.netbeans.ProxyURLStreamHandlerFactory
(file:/usr/share/netbeans/platform18/lib/boot.jar) to field java.net.URL.handler
WARNING: Please consider reporting this to the maintainers of
org.netbeans.ProxyURLStreamHandlerFactory
WARNING: Use --illegal-access=warn to enable warnings of further illegal
reflective access operations
WARNING: All illegal access operations will be denied in a future release
}}}
In an attempt to get more information about where the crash is
occurring, I ran NetBeans with -J-verbose (thus causing the JVM to
output which classes are loaded, perhaps indicating how far it got with
initialisation before the crash); the resulting file is attached as
netbeans-J-verbose.txt. Under this configuration, it consistently
crashes almost immediately after loading sun.awt.X11.XSystemTrayPeer.
(I've been testing with the Java 8 versions of java and javac.) This
might or might not be a useful lead.
Are there any tests that might give more useful information than the
limited information I have here?
This behaviour started immediately after an upgrade from Artful to
Bionic. I'm running Cinnamon as my desktop.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netbeans 8.1+dfsg3-4
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Wed Jun 13 17:57:19 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-01-31 (497 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PackageArchitecture: all
SourcePackage: netbeans
UpgradeStatus: Upgraded to bionic on 2018-06-13 (0 days ago)
** Affects: netbeans (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776724
Title:
NetBeans crashes on startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/1776724/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1207000] Re: Maximus causes windows to stop painting
What I suspect is the same issue is happening to me (I'm using a fairly different configuration from the reporter, Cinnamon on Ubuntu Artful, so it's fairly unlikely that the desktop configuration is to blame). I've also confirmed that the theme used doesn't matter, via testing with multiple different themes for window borders and window controls. The symptoms are that with Maximus running (I normally use «maximus -s -m» for testing), maximising a window sometimes causes it to become entirely invisible/transparent; it still reacts to keypresses and mouse clicks normally, and things like drop-down menus render when they should, it's just that the window doesn't render, instead showing what's "behind" it. Unlike the initial reporter, the bug acts unreliably for me (maybe there's a race condition or the like involved?). I've done most of my tests using Seahorse (a generic GTK program), and discovered that maximising the window with Alt-F10, Alt-Space X or with the "maximise" button on the title bar nearly always causes it to render correctly, whereas double-clicking the title bar normally reproduces the bug, although only the first time that that I do it for any given Seahorse window. However, I've had periods of time where I couldn't reproduce the bug with Seahorse at all, although that seems to be rare. I've also had periods of time where double-clicking the Seahorse title bar makes it turn invisible every time I do that (with the other forms of maximising working correctly), even with the same window; and one of those periods ended spontaneously after maximising with double-click and unmaximising with Alt-F10 about 3 times. Meanwhile, results with some other programs: Firefox nearly always reproduces the bug (i.e. no matter how I maximise the Firefox window, it turns transparent); the only times I've managed to successfully (i.e. without causing the bug) undecorate Firefox using Maximus have been when it's maximised as a consequence of Maximus (without -m) loading. Evolution tends to reproduce the bug if maximised via any means but the maximise button in the title bar or the maximise button on the taskbar context menu (although occasionally the bug will occur even if the maximise button is used; there seems to be no pattern here, you can do the same thing twice in a row and get different results). Kate (a KDE application, unlike the GTK applications mentioned earlier) seems to have similar results to Firefox, but with the added weird side effect (that doesn't occur with the other programs I mentioned, nor with Maximus not running) that it appears to lose window focus when unmaximised (with some other window getting it instead). Use of «xwininfo» seems to imply that the invisible maximised windows are undecorated (as they should be when using Maximus) and in the expected place on the screen, just not rendering (or rendering invisibly) for some reason. I've been unable to get at Maximus' version number from the program itself; running «maximus -v», which should report it, simply starts Maximus instead. dpkg claims that the package from which it's installed is version 0.4.14-4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1207000 Title: Maximus causes windows to stop painting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maximus/+bug/1207000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676169] Re: rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error when compiling with std
This bug appears to have been fixed in Ubuntu Zesty by a recent update: Confirmed still buggy in: 1.16.0+dfsg1-1~exp1ubuntu1 Confirmed not buggy in: 1.17.0+dfsg2-8~ubuntu0.17.04.1 I'm subscribed to -backports but not -proposed. As such, updating from -backports is likely to fix the issue for anyone else who has it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676169 Title: rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error when compiling with std To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1676169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676169] Re: rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error when compiling with std
Same issue is happening to me. Here are minimal steps to reproduce: Create an empty directory containing a single file "main.rs", containing the following single line: extern crate arena; Then, with that directory as the current directory, run: rustc main.rs The error is "error[E0523]: found two different crates with name `std` that are not distinguished by differing `-C metadata`. This will result in symbol conflicts between the two.". The use of "arena" here is not critical; any stable, public crate that's part of the standard library will do (e.g. for the original reporter, it happened with "proc_macro"). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676169 Title: rustc (1.16.0+dfsg1-1~exp1ubuntu1) gives an error when compiling with std To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rustc/+bug/1676169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Just to clarify why this bug has so many me-too votes: the bug happened once to me, during an update, and never happened again (i.e. it fixed itself, and I can print just fine, etc.). I subscribed to this thread because I was curious as to what was going on, and I did see the problem myself once but the bug doesn't have any ongoing effect on me and I can't reproduce it. I suspect that the majority of the people who have confirmed the bug are in the same boat, whereas some people here have the issue recurring for some reason. (It's unclear why; either there's something relevantly different about their configuration, or this is actually two different bugs with the same symptoms.) So although there are a lot of people here, I suspect rather fewer people are in a position to test the fix; I can't reproduce the bug, and thus there's no point in me testing the fix, as a working fix would look the same as a fix that had no effect at all. Would it be reasonable for people in my position to retract our confirmations of the bug, if we can no longer reproduce? Or is it best to leave the confirmation there, because I definitely did see the bug happen, once? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615732] Re: Execution of filter 'Junk check' fails with "Empty cache file"
I haven't seen this happen on my Ubuntu system for a while. I'm now on Evolution 3.22.3 and Ubuntu 16.10, so I'm guessing it was fixed when a newer version of Evolution was included in Ubuntu via the normal release process. As for how long these things take to get fixed after an upstream fix, it basically depends on whether the distribution consider the bug important enough to warrant an update or backport (doing these is always somewhat risky, because there's the chance that a fix for one bug could end up unintentionally breaking something else, and there's a definite desire that the system should not become worse as the result of an update). Possibilities on Ubuntu involve pushing the bugfix to everyone (this normally only happens if it's a really big problem or a security problem); pushing the bugfix only to people who've opted in to receiving backports faster; pushing the bugfix only to people who have opted into "proposed changes" to the OS (although I don't know for certain, this is typically done if pushing the change more widely is considered a good idea but there's a worry that something might break in the process); or only pushing the changes out with the next version of the OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615732 Title: Execution of filter 'Junk check' fails with "Empty cache file" To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1615732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589472] Re: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install
Same issue is happening to me, although in my case it's happening on attempts to upgrade or remove rather than on initial install. Here's what happens (the .deb file in question is a security update that was obtained from the Ubuntu archives using apt and should be the latest version): $ sudo dpkg -i /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb Selecting previously unselected package nvidia-opencl-icd-340:i386. (Reading database ... 817449 files and directories currently installed.) Preparing to unpack .../nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: warning: subprocess old pre-removal script returned error exit status 5 dpkg: trying script from the new package instead ... dpkg: error processing archive /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb (--install): there is no script in the new version of the package - giving up Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.23-0ubuntu4) ... Errors were encountered while processing: /var/cache/apt/archives/nvidia-opencl-icd-340_340.98-0ubuntu0.16.04.1_i386.deb $ sudo dpkg -r nvidia-opencl-icd-340:i386 (Reading database ... 817447 files and directories currently installed.) Removing nvidia-opencl-icd-340:i386 (340.96-0ubuntu3.16.04.1) ... Failed to stop var-lib-snapd-lib-gl.mount: Unit var-lib-snapd-lib-gl.mount not loaded. dpkg: error processing package nvidia-opencl-icd-340:i386 (--remove): subprocess installed pre-removal script returned error exit status 5 Failed to get unit file state for var-lib-snapd-lib-gl.mount: No such file or directory var-lib-snapd-lib-gl.mount is a disabled or a static unit, not starting it. Processing triggers for libc-bin (2.23-0ubuntu4) ... Errors were encountered while processing: nvidia-opencl-icd-340:i386 Incidentally, I have no idea why the package in question is on my system in the first place. It doesn't appear to be a dependency of anything (neither apt nor dpkg complains when I try to remove it), and I don't have an NVidia graphics card, so I'd have had no reason to install it manually. /var/lib/snapd/lib/gl (which seems to be relevant due to the "Unit var- lib-snapd-lib-gl.mount" message) exists, but is an empty directory. Nothing appears to be mounted there. ** Summary changed: - package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 failed to install + package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 cannot be installed, removed or upgraded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589472 Title: package nvidia-opencl-icd-340 340.96-0ubuntu3.16.04.1 cannot be installed, removed or upgraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1589472/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615732] [NEW] Execution of filter 'Junk check' fails with "Empty cache file"
Public bug reported: I currently use an Evolution setup in which I retrieve email via IMAP from an unfiltered mailbox, and then use Evolution to automatically filter for spam/junk mail. This process works as expected upon starting Evolution: all email is retrieved from the mailbox (and thus resides in the Inbox folder, where it arrived), then it's filtered to identify spam, and then the spam is moved from the Inbox to a Junk folder. However, after Evolution has been running for some time (hard to estimate because it requires an email to be received, but likely 5-10 minutes; it's possible that this is just "one email refresh interval" but also possible that something else is going on), newly received email stops being filtered for spam, and all the email remains in the Inbox. This happens at least in the case of receiving one email at a time, and most likely in the case where multiple emails are received in one send/receive cycle. When this failure to remove spam/junk happens, there's a yellow banner at the top of the screen saying, for example (the filename is not always the same), "Error while performing operation. Execution of filter 'Junk check' failed: Empty cache file: /home/ais523/.cache/evolution/mail/1440221975.23984.44@tundra/folders/INBOX/cur/1f/23052" I checked the contents of the file in question; it appears to be a copy of the email that was just received, including all headers. (It's possible that there's a race condition here and that the file was empty when the filter looked at it, but became populated just after it errored out, but perhaps something else is going on.) This behaviour is a problem because it means that either I have to delete junk mail by hand, or else that I have to repeatedly close and reopen Evolution so that the automated system will work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: evolution 3.18.5.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 22 17:19:59 2016 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2014-06-03 (811 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_GB.UTF-8 LANGUAGE=en_GB:en XDG_RUNTIME_DIR= SourcePackage: evolution UpgradeStatus: Upgraded to xenial on 2016-05-02 (112 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615732 Title: Execution of filter 'Junk check' fails with "Empty cache file" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1615732/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
OK, after discussion on the upstream mailing lists, we've concluded that the bug causing the reset loop is in the device itself (that it is failing to respect the USB protocols), but that the buggy part of the Osprey 2 Mini is related to installing the Windows and Mac OS X drivers, which aren't needed by Linux. It's possible to blacklist the buggy part (which does not work under Linux even when the reset loops don't happen) via changing a module parameter; this causes the buggy part (the driver installation) to fail, thus allowing the part that most users are using the device for (the Internet connection) to work. While the system is running, this can be achieved via the following command: $ echo 1bbb:f000:i | sudo tee /sys/module/usb_storage/parameters/quirks (The 1bbb:f000 is specific to the device in question, so it shouldn't have effects on other devices.) I've tested this on the mainline kernel, and it seems to prevent the bug from occurring. I suspect that the same would occur on Ubuntu kernels, but have not tested this yet (I can test it if you think that would be helpful). It might also be possible to set the parameter in question (usb_storage.quirks=1bbb:f000:i) via the kernel command line or configuration; I don't know of a method other than telling the bootloader to set it, which would be far too intrusive a solution for a problem that won't affect most users, but there might be a less intrusive one. This would have the advantage of preventing a crash (on an Ubuntu kernel) if the device were attached during boot. Eventually the Ubuntu kernel is likely to catch up to upstream, meaning that the impact would be much lower and people could just disconnect and reconnect the device to work around this situation. I think it might be worthwhile to get Ubuntu to set the parameter in question automatically in order to fix the bug. However, I'm not sure where the best place to set it would be. The obvious thing to do is to use /etc/sysctl.d, but unfortunately it only seems to affect /proc files rather than /sys files (and the /proc/sys tree and /sys trees are different). Alternatively, if it's possible to set default module arguments in the kernel configuration, that would be another good place. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Just as a followup: the workaround command I gave only works if the usb_storage module is already loaded. If it isn't loaded, you can write it like this: sudo modprobe usb_storage quirks=1bbb:f000:i Probably it's best to set a default parameter for the module, though, if that's possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
My email to the mailing list is archived here: http://marc.info/?l =linux-usb=145812520514664=2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
I have sent the email. I will check the mailing list archives on occasion, and provide a link when it becomes available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
$ usb-devices I've attached the output of the command. ** Attachment added: "output from usb-devices" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4600769/+files/usb-devices.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
OK, testing on the most recent mainstream kernel, 4.5.0, is now complete. The Ubuntu and kernel version: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 15.10 Release:15.10 Codename: wily $ uname -a Linux tundra 4.5.0-040500-generic #201603140130 SMP Mon Mar 14 05:32:22 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux The bug is partially fixed, and partially present: - The reset loops still occur intermittently when the device is connected. - However, unplugging the device during a reset loop no longer causes a kernel panic or hang. (There isn't any observable "action that happens instead"; the device stops resetting but that isn't surprising, given that it's no longer physically connected to the computer.) I have used both fixed-upstream and exists-upstream tags because there is still a bug with recognising the device upstream, but the worst symptom (the panic) appears to have been fixed, leaving only a more minor symptom. (This is the same behaviour that I observed when running Ubuntu Vivid.) If this is incorrect, feel free to correct the tags. The syslog from this boot, on which I plugged and unplugged the device repeatedly, is attached. ** Attachment added: "syslog for repeated connection and disconnection on a mainstream kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4600707/+files/syslog ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-fixed-upstream kernel-fixed-upstream-3.5 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Thanks for your advice. I will test the recent mainstream kernels in a few days, but I am not able to do so immediately. I will leave the bug as incomplete until then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Oh, and recovering from a reset loop spontaneously doesn't always happen, on an earlier occasion, I was stuck in a reset loop for several minutes before I decided to disconnect the device to see if, when and how the system would crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Thanks. I found the update in question. (It seems that some HP BIOS updates install on Linux, and others require Windows; luckily I had a dual-boot setup available to install it.) $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date F.68 09/21/2015 I can confirm that the issue still occurs. I also determined some further information: - The hangs are definitely triggered upon disconnecting the device (or turning it off) during a reset loop. This has a 100% correlation so far; if it's not in a reset loop when I disconnect it (even if there was a loop earlier), the kernel is fine, and if it's in a reset loop but I don't disconnect it, the kernel is also fine. - The kernel/device have, on occasion, recovered from a reset loop "spontaneously" after several seconds. (This has happened twice now.) My current boot is one such occasion; I attached the device while the system was booting (reasonably late in the boot sequence), and the reset loop stopped after a while. I've attached the syslog from this boot session, in case it helps. - I managed to catch one of the non-panic hangs (i.e. computer responds to no input, not even Alt-SysRq combinations, but the Caps Lock light does not flash) while on the Ctrl-Alt-F1 text terminal. It happened when I disconnected the Osprey Mini 2 during a reset loop, and started (as happens in other cases) with text scrolling far too fast to read. Then it stabilized into displaying messages about CPUs being stuck every 20s or so. One of them was along the lines of "CPU #2 HARD lockup" (I forget the exact phrasing, and didn't have time to write it down or take a photograph); all the others mentioned other CPUs (mostly CPU #3). The error message for CPU #3 was always almost the same: NMI watchdog: BUG: CPU #3 stuck for 22s! [apache2:4544] (the time shown changed on occasion, sometimes it was 21s) The information only stayed onscreen for a limited time, so I couldn't write much down; I decided that the top of the stack trace would probably be the most helpful piece of information for debugging: queue_read_lock_slowpath+0x92/0xa0 _raw_read_lock+0x1c/0x20 no_wait [I didn't write down the offsets from here on so that I could get more of the stack] SyS_wait4 ? _task_stopped_code Additionally, after a while of this, the CPU fan settled on a speed that it normally reaches if 1 of my 4 cores is running at 100% and the others are all idle. It thus seems most likely that CPU #2 was in a tight loop, and the other CPUs were blocking on locks that CPU #1 held, thus preventing the system making any progress. - The error message in the panic case is not always the same. I've seen a few different stacktraces, and although I can't remember the details, they were definitely different each time. ** Attachment added: "system spontaneously recovering from a reset loop" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+attachment/4599246/+files/syslog ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
The most recent BIOS offered via the page you linked was F.66. I updated my BIOS to that version: $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date F.66 07/01/2014 After updating, I connected and disconnected the Osprey 2 Mini four times, with no crashes. Then I rebooted, connected it and got a reset loop, and disconnected it and got a system hang (Caps Lock was not flashing but the system did not respond to any input, not even Alt- SysRq-B, and I had to hold down the power button to shut it off). As such, I believe the BIOS update did nothing to prevent the bug occurring, and that the bug is still present. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
The sticker on the computer itself is reasonably cryptic: Product: F9E45EA#ABU Model: 15-n298sa I also checked the box the computer came in. It contains the same product and model numbers, and additionally the description "HP Pavilion 15 Notebook PC". ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Some more log files I got experimenting. Here's a kern.log excerpt for a successful (i.e. intended behaviour, no visible bug reproduction) connection of the device (I included every line from the relevant time period because I'm not 100% sure which are relevant): Mar 13 03:09:27 tundra kernel: [ 91.132481] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 13 03:09:27 tundra kernel: [ 91.245683] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 13 03:09:27 tundra kernel: [ 91.245689] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 13 03:09:27 tundra kernel: [ 91.245691] usb 3-1.2: Product: MobileBroadBand Mar 13 03:09:27 tundra kernel: [ 91.245693] usb 3-1.2: Manufacturer: Alcatel Mar 13 03:09:27 tundra kernel: [ 91.245695] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 13 03:09:27 tundra kernel: [ 91.338218] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 13 03:09:27 tundra kernel: [ 91.338719] scsi host6: usb-storage 3-1.2:1.0 Mar 13 03:09:27 tundra kernel: [ 91.338900] usbcore: registered new interface driver usb-storage Mar 13 03:09:27 tundra kernel: [ 91.354544] usbcore: registered new interface driver uas Mar 13 03:09:27 tundra kernel: [ 91.377716] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.377752] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8610 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.388020] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8612 LEN=24 Mar 13 03:09:27 tundra kernel: [ 91.388070] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1 FLOWLBL=0 PROTO=UDP SPT=8612 DPT=8610 LEN=24 Mar 13 03:09:28 tundra kernel: [ 92.338460] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:28 tundra kernel: [ 92.339441] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:28 tundra kernel: [ 92.340452] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 13 03:09:28 tundra kernel: [ 92.350362] sr 6:0:0:1: [sr1] scsi-1 drive Mar 13 03:09:28 tundra kernel: [ 92.350592] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 13 03:09:28 tundra kernel: [ 92.350733] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 13 03:09:28 tundra kernel: [ 92.363363] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 13 03:09:28 tundra kernel: [ 92.444043] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 13 03:09:28 tundra kernel: [ 92.643995] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 13 03:09:35 tundra kernel: [ 99.016607] usb 3-1.2: USB disconnect, device number 3 Mar 13 03:09:35 tundra kernel: [ 99.245827] usb 3-1.2: new high-speed USB device number 4 using ehci-pci Mar 13 03:09:35 tundra kernel: [ 99.360175] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=0195 Mar 13 03:09:35 tundra kernel: [ 99.360181] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 13 03:09:35 tundra kernel: [ 99.360183] usb 3-1.2: Product: MobileBroadBand Mar 13 03:09:35 tundra kernel: [ 99.360185] usb 3-1.2: Manufacturer: Alcatel Mar 13 03:09:35 tundra kernel: [ 99.360187] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 13 03:09:35 tundra kernel: [ 99.382621] usb-storage 3-1.2:1.2: USB Mass Storage device detected Mar 13 03:09:35 tundra kernel: [ 99.382837] scsi host7: usb-storage 3-1.2:1.2 Mar 13 03:09:35 tundra kernel: [ 99.439524] usbcore: registered new interface driver cdc_ether Mar 13 03:09:35 tundra kernel: [ 99.467466] rndis_host 3-1.2:1.0 usb0: register 'rndis_host' at usb-:00:1a.0-1.2, RNDIS device, 46:c4:64:00:d0:da Mar 13 03:09:35 tundra kernel: [ 99.467592] usbcore: registered new interface driver rndis_host Mar 13 03:09:35 tundra kernel: [ 99.484172] rndis_host 3-1.2:1.0 enx46c46400d0da: renamed from usb0 Mar 13 03:09:35 tundra kernel: [ 99.521306] IPv6: ADDRCONF(NETDEV_UP): enx46c46400d0da: link is not ready Mar 13 03:09:36 tundra kernel: [ 100.383747] scsi 7:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 13 03:09:36 tundra kernel: [ 100.384133] sd 7:0:0:0: Attached scsi generic sg2 type 0 Mar 13 03:09:36 tundra kernel: [ 100.391751] sd 7:0:0:0: [sdb] Attached SCSI removable disk Mar 13 03:09:36 tundra kernel: [ 100.462051] [UFW BLOCK] IN=wlan0 OUT= MAC= SRC=fe80::::9ed2:1eff:fe03:ad17 DST=ff02:::::::0001 LEN=64 TC=0 HOPLIMIT=1
[Bug 1556471] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597147/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597153/+files/UdevLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597152/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597149/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597154/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597151/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597148/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
apport-collect has attached the requested files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597150/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597141/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597144/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597142/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597145/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597143/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1556471/+attachment/4597146/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556471 Title: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1556471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] Re: Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
apport information ** Tags added: apport-collected wily ** Description changed: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra usb_modeswitch_dispatcher[11944]: Error: could not get description string "serial number" Mar 11 20:37:07 tundra usb_modeswitch: switch device 1bbb:f000 on 003/003 Mar 11 20:37:07 tundra kernel: [20659.328319] scsi 6:0:0:0: rejecting I/O to offline device Mar 11 20:37:07 tundra kernel: [20659.328412] scsi 6:0:0:0: killing request Mar 11 20:37:13 tundra systemd-udevd[11969]: inotify_add_watch(9,
[Bug 1191238] Re: Color palette resets to default upon losing focus
And still fixed on Wily. I think Ubuntu has pulled in the upstream fix and there's nothing more to change now. ** Changed in: gnome-terminal (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556471] [NEW] Connecting an Osprey 2 Mini (USB cellular wireless router) sometimes causes an endless reset loop or a kernel panic
Public bug reported: Steps to reproduce (happens > 50% of the time, but not every time): Turn on an Osprey 2 Mini Connect it to a USB port via a USB cable while both the device and computer are on (i.e. hotplug) Observed symptoms: - sometimes the Osprey 2 Mini goes into an endless reset loop (visible as the LEDs on the front of the device flashing rapidly), being reset approximately every 200ms; on such occasions, the Ubuntu user interface often reacts as though I'd inserted an audio CD containing corrupted data (e.g. via repeteadly adding an "Audio CD" icon to the launcher and then removing it, and putting up dialog boxes complaining about failure to read the data) - sometimes the kernel panics (often some time after the reset loop starts, perhaps up to 10 seconds); when this happens there was always or nearly always a reset loop occurring beforehand - sometimes the device resets once or not at all, then works as expected (showing up as a network interface, and allowing me to communicate to the Internet with a wired connection); I'm currently using an Osprey 2 Mini for this purpose right now I haven't been able to gain much information about the source of the kernel panics, as they lock up the entire system (forcing a hard power off). Alt-Sysrq commands don't work in this state (even though I have them enabled), and sometimes the Caps Lock light flashes repeatedly, both signs of a panic. The logs end some time before the panic occurs; presumably the panic means that the log file is never written to disk. Looking at my logs retrospectively, here's an interesting/relevant portion of /var/log/syslog: Mar 11 20:37:04 tundra kernel: [20656.424192] usb 3-1.2: new high-speed USB device number 3 using ehci-pci Mar 11 20:37:04 tundra kernel: [20656.549351] usb 3-1.2: New USB device found, idVendor=1bbb, idProduct=f000 Mar 11 20:37:04 tundra kernel: [20656.549362] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Mar 11 20:37:04 tundra kernel: [20656.549367] usb 3-1.2: Product: MobileBroadBand Mar 11 20:37:04 tundra kernel: [20656.549371] usb 3-1.2: Manufacturer: Alcatel Mar 11 20:37:04 tundra kernel: [20656.549375] usb 3-1.2: SerialNumber: 0123456789ABCDEF Mar 11 20:37:02 tundra gnome-session[5167]: message repeated 19 times: [ log_kalarm:] Mar 11 20:37:05 tundra mtp-probe: checking bus 3, device 3: "/sys/devices/pci:00/:00:1a.0/usb3/3-1/3-1.2" Mar 11 20:37:05 tundra mtp-probe: bus: 3, device: 3 was not an MTP device Mar 11 20:37:05 tundra systemd[1]: Created slice system-usb_modeswitch.slice. Mar 11 20:37:05 tundra systemd[1]: Starting USB_ModeSwitch_3-1.2... Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: Could not read attribute: No such file or directory Mar 11 20:37:05 tundra kernel: [20657.479875] usb-storage 3-1.2:1.0: USB Mass Storage device detected Mar 11 20:37:05 tundra kernel: [20657.480088] scsi host6: usb-storage 3-1.2:1.0 Mar 11 20:37:05 tundra kernel: [20657.480291] usbcore: registered new interface driver usb-storage Mar 11 20:37:05 tundra kernel: [20657.528383] usbcore: registered new interface driver uas Mar 11 20:37:06 tundra kernel: [20658.481811] scsi 6:0:0:0: Direct-Access ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.482801] scsi 6:0:0:1: CD-ROM ONETOUCH LINK42.31 PQ: 0 ANSI: 2 Mar 11 20:37:06 tundra kernel: [20658.483902] sd 6:0:0:0: Attached scsi generic sg2 type 0 Mar 11 20:37:06 tundra kernel: [20658.495442] sr 6:0:0:1: [sr1] scsi-1 drive Mar 11 20:37:06 tundra kernel: [20658.496665] sr 6:0:0:1: Attached scsi CD-ROM sr1 Mar 11 20:37:06 tundra kernel: [20658.496740] sd 6:0:0:0: [sdb] Attached SCSI removable disk Mar 11 20:37:06 tundra kernel: [20658.496914] sr 6:0:0:1: Attached scsi generic sg3 type 5 Mar 11 20:37:06 tundra kernel: [20658.587460] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.795437] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20658.999352] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:07 tundra kernel: [20659.207280] usb 3-1.2: reset high-speed USB device number 3 using ehci-pci Mar 11 20:37:05 tundra usb_modeswitch_dispatcher[11944]: message repeated 2 times: [ Could not read attribute: No such file or directory] Mar 11 20:37:07 tundra usb_modeswitch_dispatcher[11944]: Error: could not get description string "serial number" Mar 11 20:37:07 tundra usb_modeswitch: switch device 1bbb:f000 on 003/003 Mar 11 20:37:07 tundra kernel: [20659.328319] scsi 6:0:0:0: rejecting I/O to offline device Mar 11 20:37:07 tundra kernel: [20659.328412] scsi 6:0:0:0: killing request Mar 11 20:37:13 tundra systemd-udevd[11969]: inotify_add_watch(9, /dev/sdb, 10) failed: No such file or directory Mar 11 20:37:13 tundra kernel: [20665.683553] usb 3-1.2: USB disconnect, device number 3 Mar 11 20:37:14 tundra kernel:
[Bug 1191238] Re: Color palette resets to default upon losing focus
Cannot reproduce on Trusty. I assume the change has filtered through to Ubuntu by now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203414] Re: evolution crashes shortly after opening when evolution-indicator is installed
Cannot reproduce on trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330956] [NEW] high score tables are always empty
Public bug reported: When freshly installing glines/five-or-more, the high score tables stay empty even when games are completed. Expected behaviour is for newly completed games to appear in the high score table if they have a higher score than the currently lowest-scoring game on the table. The direct cause of this is incorrect permissions on the high score tables; the current five-or-more package installs /var/games/glines.*.scores as 644 root/root, and the correct permissions are 664 root/games (as seen in many other game-related packages). (The 2755 root/games permissions on the executable itself are correct.) The indirect cause is that there's an attempt made to install the high score tables in fresh installs via two different mechanisms; the postinst configure script tries to install them with the correct permissions, but it leaves the files as they currently are if they already exist; the binary package also tries to install them directly during unpack, but with the incorrect permissions. Unpack happens before configure, so first the unpack creates the files with the wrong permissions, and then the unpack leaves them alone. The provided patch fixes this issue via removing the high score files from the binary package, leaving the postinst script in charge of creating them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: five-or-more 1:3.8.2-1 [modified: var/games/glines.Small.scores] ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 17 12:23:45 2014 InstallationDate: Installed on 2014-06-03 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: five-or-more UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: five-or-more (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Patch added: patch that fixes this bug https://bugs.launchpad.net/bugs/1330956/+attachment/4133225/+files/fix-high-score-permissions.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330956 Title: high score tables are always empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/five-or-more/+bug/1330956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268419] Re: mumble freezes in audio tuning wizard
Further information: Mumble quits upon SIGTERM, it doesn't require a SIGKILL (indicating, most likely, an infinite loop). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268419 Title: mumble freezes in audio tuning wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1268419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268419] [NEW] mumble freezes in audio tuning wizard
Public bug reported: When using the Audio Tuning Wizard, Mumble freezes with 100% CPU usage after clicking on Next on the Device selection screen (the first screen on which settings can be changed). Expected behaviour is for it to move to the next screen of the wizard. The notification area shows red lips when this operation is performed. I went through this wizard during initial setup of Mumble, and noticed nothing unusual; this problem only occurred upon attempting to reconfigure the audio on a subsequent use. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: mumble 1.2.3-349-g315b5f5-2.2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Sun Jan 12 23:39:08 2014 ExecutablePath: /usr/bin/mumble InstallationDate: Installed on 2009-12-14 (1490 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: mumble UpgradeStatus: Upgraded to saucy on 2013-11-06 (67 days ago) ** Affects: mumble (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268419 Title: mumble freezes in audio tuning wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1268419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268419] Re: mumble freezes in audio tuning wizard
I managed to work around this bug by changing both input and output to use ALSA rather than PulseAudio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268419 Title: mumble freezes in audio tuning wizard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1268419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 651267] Re: Audio output consumes 100% cpu and no red lips
#1268419 may or may not be a duplicate. If it is, changing to ALSA rather than PulseAudio may be a workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/651267 Title: Audio output consumes 100% cpu and no red lips To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/651267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203414] Re: evolution crashes shortly after opening when evolution-indicator is installed
I just checked on saucy. The bug is still reproducible (evolution crashes with evolution-indicator installed, does not crash if evolution- indicator is not installed). ** Tags added: saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191238] Re: Color palette resets to default upon losing focus
Just tested on saucy; I can still reproduce this bug. ** Tags added: saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203414] Re: evolution crashes shortly after opening
Followup: I tried running Evolution in a terminal, and opening a message via double-click to reproduce the crash. I've attached the output that it spewed to the terminal. ** Attachment added: output sent to the terminal via evolution (probably stderr, may be stdout, I didn't redirect them separately) https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1203414/+attachment/3744053/+files/evolution-stderr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203414] [NEW] evolution crashes shortly after opening when evolution-indicator is installed
Public bug reported: Immediately after upgrading to raring, Evolution crashes soon after loading. I'm not sure what the specific trigger is; sometimes it crashes within under a second even with no action from me, sometimes it lasts up to a minute or so. It tends to crash reliably when I attempt to view any message (via the message preview, or via double-clicking on it with the message preview turned off), though it sometimes also seems to crash due to other triggers; I sometimes see the content of the message for a tiny fraction of a second before the crash. It has managed to receive new emails in the short length of time while it's been open (although I haven't been able to observe what those emails are). The visible symptom is that Evolution simply closes (or, on one occasion, was greyed out by Compiz due to being a stuck process, and had to be force-quit). apport has since stopped bothering to collect crash dumps, but I've attached one of the crash dumps it did collect to this bug report. Hopefully that will provide more information as to the nature of the problem (and what specific sort of crash is involved). Expected behaviour is for Evolution to show me the content of the message without crashing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evolution 3.6.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic i686 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 Date: Sun Jul 21 03:52:55 2013 InstallationDate: Installed on 2009-12-14 (1314 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to raring on 2013-07-21 (0 days ago) ** Affects: evolution-indicator (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring ** Attachment added: _usr_bin_evolution.1000.crash https://bugs.launchpad.net/bugs/1203414/+attachment/3744051/+files/_usr_bin_evolution.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1203414] Re: evolution crashes shortly after opening
The crash appears to be in evolution-indicator from the backtrace, and went away when I uninstalled evolution-indicator, so that's a good guess as to the culprit ** Package changed: evolution (Ubuntu) = evolution-indicator (Ubuntu) ** Summary changed: - evolution crashes shortly after opening + evolution crashes shortly after opening when evolution-indicator is installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1203414 Title: evolution crashes shortly after opening when evolution-indicator is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-indicator/+bug/1203414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1191238] [NEW] Color palette resets to default upon losing focus
Public bug reported: gnome-terminal understands the control codes (CSI ] 4 ; … ST) for changing the color palette available to console applications. However, when the current tab loses focus (either because the gnome-terminal window loses focus, or because I switch to a different tab), any custom color palette installed by the console application I'm using are lost, and it resets to the palette set in the profile. Steps to reproduce: Profile settings: Use colors from system theme off, Built-in schemes: custom, any custom text and background color, any built-in color scheme. (I've tested multiple settings for the actual colors; none have an effect on the bug reproducibility. I haven't tested using colors from the system theme, or a built-in scheme, but I suspect they also don't influence whether they bug can be reproduced. Load up bash inside the terminal, using a prompt that does not set colors, and run the following command: printf '\x1b[91m' This sets the foreground color to 9 (light red); the subsequent text in the terminal turns light red (this is both observed and expected behaviour). Then run the following command: printf '\x1b]4;9;rgb:00/00/ff\x1b\\' This redefines color 9 to be bright blue. The subsequent text in the terminal turns bright blue (again, this is both observed and expected behaviour). Now, switch to a different tab, or a different application, then back to gnome-terminal. (If you switch to a different application that does not overlap gnome-terminal, you can see the color change happen onscreen.) I'm on a system (Unity) where keyboard focus always follows window focus, so I'm not sure if the trigger is losing keyboard focus or window focus; if you have a different window manager, you might want to test both separately. Expected behaviour: the bright blue text remains bright blue upon switching away from the window, and continues to remain bright blue when returning to the window. Text continues to be bright blue unless the foreground color or palette are changed again. Observed behaviour: the bright blue text becomes light red upon switching away from the window, and continues to remain light red upon returning to the window. Text continues to be light red unless the foreground color or palette are changed again. Changing palette entries other than 9 does not cause the text to become blue again; nor does changing the foreground color away from 9 and then back to 9. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-34.55-generic 3.5.7.13 Uname: Linux 3.5.0-34-generic i686 ApportVersion: 2.6.1-0ubuntu11 Architecture: i386 Date: Sat Jun 15 09:25:32 2013 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2009-12-14 (1278 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MarkForUpload: True ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-10-18 (239 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal running-unity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1191238 Title: Color palette resets to default upon losing focus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1191238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012985] [NEW] pan creates PEM certificates in my home directory with garbage filenames
Public bug reported: In my home directory, several PEM certificates were created, mostly with the same content (I've only observed two different versions). Both of the versions I've seen, when un-base64-ed, appear to be certificates for my news server; I haven't been accessing it (over any protocol) via any application but pan, so it must be to blame. (I haven't caught the files in the act of being created, though.) The names strongly look like uninitialised data. (I moved the certificates out of my home directory to avoid clutter, but kept the files around for further testing): $ ls -b1 ~/garbage_pem_files/ \ \ \ \ - \002 \004 \025 \2404\226 ml operation_block_and_unref:\ 0x972bec0:\ done process.binary @\327\020\266\220Q\021\266\025 \274r\002 ral top_general ب I run Pan from the launcher, meaning that its working directory is my home directory, so it's possible it's creating them in the working directory instead. It doesn't seem to create the files on every run, either; the bug's intermittent. (It has been crashing unexpectedly from time to time too, which might or might not be relevant; next time it crashes, I'll check to see if a PEM file was created.) Possibly relevant options: Use Secure SSL Connections and Always trust this server's certificate on the only news server it's configured to use. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pan 0.136-1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic i686 ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 Date: Thu Jun 14 06:36:33 2012 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pan UpgradeStatus: Upgraded to precise on 2012-04-26 (48 days ago) ** Affects: pan (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012985 Title: pan creates PEM certificates in my home directory with garbage filenames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pan/+bug/1012985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1012985] Re: pan creates PEM certificates in my home directory with garbage filenames
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1012985 Title: pan creates PEM certificates in my home directory with garbage filenames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pan/+bug/1012985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005007] Re: evolution takes forever to retrieve new messages
Can no longer reproduce, presumably because the offending IMAP server has started working again. This bug may well require access to a broken IMAP server for testing; I'm not entirely sure where I could get one, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005007] [NEW] evolution takes forever to retrieve new messages
Public bug reported: Evolution, when I click on send/receive messages, or automatically when I view a particular IMAP mailbox (which is set to make messages available offline, which might or might not be relevant), spends forever (several hours so far, and I have no reason to think it will end) with Retrieving message '19464' from INBOX (twice), Retrieving message '18840' from INBOX, Refreshing folder INBOX, and Checking for new mail as progress items in the status bar. That particular mailbox lists messages it contains but just displays Retrieving message '19464' in the place where the email itself is normally displayed when I try to view the most recent email when clicking on it (and adds another copy of Retrieving message '19464' from INBOX to the status bar); the rest of the interface, and other mailboxes, work correctly. Evolution is also using an appreciable proportion of my CPU power. This happens consistently each time I load the program and navigate to that email. Evolution cannot be closed normally while the progress messages are shown; they just get stuck at (cancelling) and it doesn't close, not with the normal close button nor with SIGTERM (I have to resort to SIGKILL). I don't know whether or not the IMAP server I'm trying to connect to is having issues, and it seems likely that it is, given that my other IMAP mailboxes work fine. Nonetheless, Evolution should not be unresponsive in this way no matter how the server it's connecting to responds. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: evolution 3.2.3-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 26 23:37:36 2012 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: evolution UpgradeStatus: Upgraded to precise on 2012-04-26 (30 days ago) ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005007] Re: evolution takes forever to retrieve new messages
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005007] Re: evolution takes forever to retrieve new messages
Oh, and just checked: the list of emails shown in the problematic mailbox is the list as of the last time the mailbox worked, it doesn't account for emails received since. (Emails related to this bug are going into that mailbox; that's how I noticed.) I can also access the mailbox in question via a web browser, so I should still be able to communicate about the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1005007] Re: evolution takes forever to retrieve new messages
One more experiment: if I reboot the system and then load Evolution and give it no input, nor switch to the offending mailbox, it's left with one Checking for new mail in the status bar. (There were originally four; I have four mailboxes. But three of them disappeared.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1005007 Title: evolution takes forever to retrieve new messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1005007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 548661] Re: sound only from built-in speakers, not headpones
Same bug happens to me too on a fully-updated Lucid system. It was working fine on Karmic a few months ago, on the same system (the relevant sound was flagged as [Conexant CX20582 (Pebble)] by the bug- reporting tool, the system itself is a Toshiba Satellite T110-107). Plugging in the headphones makes no apparent difference to the sound, which continues to come out via the speakers but not the headphones. This bug possibly happened on Karmic too, relatively recently; I didn't report it at the time because I wasn't sure whether it had happened or not, and because I'm not sure exactly what happened then. (This bug isn't an obvious one to check for unless you're specifically paying attention...) -- sound only from built-in speakers, not headpones https://bugs.launchpad.net/bugs/548661 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529053] [NEW] update-manager sometimes hangs at blank applying changes dialog
Public bug reported: Binary package hint: update-manager Yet another of those annoying intermittent bugs. Sometimes, when I attempt to update my system (update manager loads automatically, I click on Install Updates and then enter my gksudo password), update manager will open a window with the title Applying Changes, but no content, and then apparently hang. pgrep and top show one sleeping update-manager process (owned by me), one sleeping synaptic process (owned by root), and one zombie synaptic process (owned by root), none of which are using any CPU. Expected behaviour is for the applying-changes window to populate itself with information and show progress for the update, and the update to actually happen. This bug doesn't always happen; I'm not yet sure what triggers it. If you need any more information, just ask. ProblemType: Bug Architecture: i386 Date: Sat Feb 27 15:26:40 2010 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/update-manager InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) InterpreterPath: /usr/bin/python2.6 Package: update-manager 1:0.126.9 PackageArchitecture: all ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-20.57-generic SourcePackage: update-manager Uname: Linux 2.6.31-20-generic i686 ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- update-manager sometimes hangs at blank applying changes dialog https://bugs.launchpad.net/bugs/529053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529053] Re: update-manager sometimes hangs at blank applying changes dialog
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/39856893/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/39856894/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/39856895/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/39856896/XsessionErrors.txt -- update-manager sometimes hangs at blank applying changes dialog https://bugs.launchpad.net/bugs/529053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 529053] Re: update-manager sometimes hangs at blank applying changes dialog
This bug also seems to be capable of happening with the Check button; in that case, it hangs with only one synaptic process, and with the dialog box stuck with a complete progress bar, but not responding to any clicks. Checking with aptitude implies that in the first case, at least, the updates were actually applied; my current guess as to what's going on is that the UI sometimes hangs once the operation completes (and the progress dialog box might not have been populated due to having been minimized continuously until the update finished; this may or may not be relevant, and could certainly explain why the bug is apparently intermittent if it is). -- update-manager sometimes hangs at blank applying changes dialog https://bugs.launchpad.net/bugs/529053 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487744] Re: Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
Finally figured out what's going on here! I'm now on a different
computer, and getting the same bug again; but it behaves slightly
differently here. This computer has an ext4 filesystem originally
created by Ubuntu Karmic, and has a rather smaller main partition
(relevant to how I noticed what was going on); but the same thing's
happening. (And yes, I'm now suspicious that the blame is mostly
mountall's.)
What happens here if I don't press ESC to abort a scheduled fsck is
exactly the same; it appears to proceed as normal until 89% (which goes
very quickly on this computer, thus making it easier to test), the hard
drive activity light goes off, the fsck progress goes to 90% after
several minutes, and the system apparently completely hangs thereafter.
However, after waiting for another half-hour or so, during which the
system is apparently completely hung, the progress bar goes to 91%, and
picks up thereafter, with the boot finally completed.
Pressing ESC works differently on this machine, though; instead of
aborting the fsck, it switches to tty1, gives an error message (General
error mounting filesystems.), and drops me to a root prompt, with the
advice that control-D should retry. After pressing control-D, the fsck
resumes not at 0%, but at whatever percentage it was at when I press
ESC; it's as if the fsck was not stopped at all, but only suspended
(which, if true, would at least explain why the filesystems failed to
mount).
As a test, I tried interrupting a scheduled fsck with ESC, restarting it with
control-D, interrupting the same FSCK again, restarting it again with
control-D, and finally waiting until the fsck completed (including the huge
hang at 89-91% for no apparent reason and with no hard drive activity). This is
a dump of tty1 obtained after the boot sequence ended (obtained via /dev/vcs1):
{{{
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
r...@desert:~# exit
mountall start/starting
fsck from util-linux-ng 2.16
swapon: /dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea: swapon failed:
Device or resource busy
mountall: swapon /dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea [1003]
terminated with status 255
mountall: Problem activating swap:
/dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea
/dev/sda5 has been mounted 25 times without being checked, check forced.
Filesystem checks are in progress (ESC to cancel):
[###-]
mountall: Cancelled
/dev/sda5: e2fsck canceled.
fsck.ext4: Inode bitmap not loaded while setting block group checksum info
mountall: fsck / [1001] terminated with status 8
mountall: General fsck error
init: mountall main process (1000) terminated with status 1
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
r...@desert:~# exit
mountall start/starting
fsck from util-linux-ng 2.16
swapon: /dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea: swapon failed:
Device or resource busy
mountall: swapon /dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea [1042]
terminated with status 255
mountall: Problem activating swap:
/dev/disk/by-uuid/93f82bd9-13ba-48d0-b6e0-d56326ae15ea
/dev/sda5 has been mounted 25 times without being checked, check forced.
Filesystem checks are in progress (ESC to cancel):
/dev/sda5: 1968337/4784128 files (0.2% non-contiguous), 13948395/19129390 blocks
Ubuntu 9.10 desert tty1
desert login:
}}}
Hopefully this is enough information to debug what's going on here.
** Changed in: mountall (Ubuntu)
Status: Invalid = New
** Summary changed:
- Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
+ Scheduled fsck during boot unresponsive and inactive for a very long time at
90%, making the system appear to hang
--
Scheduled fsck during boot unresponsive and inactive for a very long time at
90%, making the system appear to hang
https://bugs.launchpad.net/bugs/487744
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505820] Re: [gm45] gnome-power-manager reports a broken display server after random screen blanking
I can't confirm in any direction, as this hasn't happened to me even on karmic for over a month. I'm not sure if the bug's fixed tiself or if it just isn't being triggered, though. Possibly it's best to mark it as WORKSFORME or whatever until or unless it recurs. -- [gm45] gnome-power-manager reports a broken display server after random screen blanking https://bugs.launchpad.net/bugs/505820 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505820] Re: gnome-power-manager reports a broken display server after random screen blanking
Hibernation appears to be irrelevant; it happened again to me on a clean boot. Additionally, there was a longer wait before the screen unblanked this time (until I moved the mouse; it's probable that it lasts until either any input, or anything that would dismiss a screensaver/unblank a screen). As with the last time it happened, and with cheoppy's report, there's nothing at all relevant in any of the logs I checked, just the screen blanking and unblanking, and the notification area warning of a bug. -- gnome-power-manager reports a broken display server after random screen blanking https://bugs.launchpad.net/bugs/505820 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505820] [NEW] gnome-power-manager reports a broken display server after random screen blanking
Public bug reported: Binary package hint: xorg My laptop screen (I'm using a Toshiba Satellite, I'm not sure which version) randomly went blank for around half a second, then turned back on again; a message was displayed in the notification area from gnome-power-manager, as follows: Session active, not inhibited, screen idle. If you can see this text, your display server is broken and you should notify your distributor. Please see http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-blanking-removal-of-bodges/ for more information. (Expected behavior is no screen blanking, and no notification message.) The blog post listed implies that the message in question appears immediately after gnome-power-manager has worked around a known X bug, and that the error should be reported upstream. However, the comments to the blog also imply that the patches in question have been applied to Ubuntu's X server already (I'm running X version 1.6.4); so it's also possible the bug is in gnome-power-manager causing a spurious notification (although that doesn't explain the screen going blank), or maybe even somewhere else affecting both components. This problem's happened exactly twice to me, seemingly for no reason (ugh intermittent bugs); the only unusual thing I was doing restoring from hibernation, rather than rebooting as usual. Sorry I don't really have much more of an idea of what's going on; if more information's needed, ask and I'll try to provide it. ProblemType: Bug Architecture: i386 Date: Mon Jan 11 09:54:21 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: TOSHIBA SATELLITE T110 Package: xorg 1:7.4+3ubuntu10 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic root=UUID=ce6fddb1-91cd-4100-b7d6-8daa69e7ffd8 ro quiet splash ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Uname: Linux 2.6.31-17-generic i686 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 09/29/2009 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.70 dmi.board.name: SATELLITE T110 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.70:bd09/29/2009:svnTOSHIBA:pnSATELLITET110:pvrPST1AE-00K00GEN:rvnTOSHIBA:rnSATELLITET110:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: SATELLITE T110 dmi.product.version: PST1AE-00K00GEN dmi.sys.vendor: TOSHIBA fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.31-17-generic ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- gnome-power-manager reports a broken display server after random screen blanking https://bugs.launchpad.net/bugs/505820 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505820] Re: gnome-power-manager reports a broken display server after random screen blanking
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/37710124/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/37710125/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/37710126/Dependencies.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/37710127/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/37710128/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/37710129/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/37710130/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/37710131/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/37710133/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/37710134/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/37710135/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/37710137/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/37710138/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/37710139/Xrandr.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/37710140/XsessionErrors.txt ** Attachment added: glxinfo.txt http://launchpadlibrarian.net/37710141/glxinfo.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/37710142/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/37710143/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/37710144/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/37710145/xkbcomp.txt -- gnome-power-manager reports a broken display server after random screen blanking https://bugs.launchpad.net/bugs/505820 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487744] Re: Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
This bug seems to have stopped occuring now (at least, I can no longer reproduce it...) Marking as invalid for the time being, I'll reopen the bug if it happens again. (It was happening repeatably earlier, though, so it seems not to be intermittent; probably it's triggering on some unknown cause.) ** Changed in: mountall (Ubuntu) Status: New = Invalid -- Scheduled fsck during boot hangs at 90%, preventing boot sequence completing https://bugs.launchpad.net/bugs/487744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487744] Re: Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
- fsck is showing a progress bar; if fsck isn't there, then how would the progress bar appear? Actually fsck doesn't show the progress bar, something else is. If fsck went away, and that something else hadn't noticed, the progress bar would be still there ... and Escape wouldn't work. I assumed the progress bar was some variant of fsck -C; in previous versions of Ubuntu, the progress bar showed a lot of detail about what the fsck was doing, although nowadays it's a simple percentage. fsck unexpectedly exiting at 90% would explain about half the symptoms I'm getting, though (although it wouldn't directly explain why the system would lock up rather than continue thereafter). -- Scheduled fsck during boot hangs at 90%, preventing boot sequence completing https://bugs.launchpad.net/bugs/487744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487744] Re: Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
I actually don't think you have an fsck at all, which would explain why Escape isn't working This can't possibly be the case: - Escape works just fine before the fsck reaches 89% - fsck is showing a progress bar; if fsck isn't there, then how would the progress bar appear? - Filesystem checks are in progress (ESC to cancel): strongly implies that something is trying to run fsck, and if it wasn't there I'd expect it to error out immediately - which fsck and which e2fsck return /sbin/fsck and /sbin/e2fsck, as expected - the bug reporting tool would have noticed if I tried to report a bug in a package I don't have installed -- Scheduled fsck during boot hangs at 90%, preventing boot sequence completing https://bugs.launchpad.net/bugs/487744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 487744] Re: Scheduled fsck during boot hangs at 90%, preventing boot sequence completing
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/36030588/Dependencies.txt -- Scheduled fsck during boot hangs at 90%, preventing boot sequence completing https://bugs.launchpad.net/bugs/487744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
