[Bug 2003204] Re: Update git because of CVE-2022-23521

[Eliah Kagan]

As shown at https://ubuntu.com/security/CVE-2022-23521, Canonical *did*
provide a fix for this, including for the three versions of Ubuntu
mentioned here (18.04 bionic, 20.04 focal, 22.04 jammy). That Ubuntu
Security Notice was published a day before this bug report was opened,
and unless I'm missing something, it looks like this bug report was
based on a misconception about how security patches and their associated
versioning works.

Most security patches in Debian, Ubuntu, and most (though not all)
distros are are provided as patched versions that add only the fix for
the security vulnerability, without new feature changes. In Ubuntu, this
relates to https://wiki.ubuntu.com/StableReleaseUpdates. That is what
https://bugs.launchpad.net/ubuntu/+source/git/+bug/2003204/comments/1
above is referring to. The fixed packages' version numbers did not match
the expectation expressed in the bug description here, but they did fix
the bug.

Of course, it can still be valuable to use ppa:git-core/ppa if one wants
the *features* of a new git version, such as performance, additional
options, more user-friendly messages, and so forth. But getting fixes
for security vulnerabilities does not generally require this, and did
not require it in the case of CVE-2022-23521.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2003204

Title:
  Update git because of CVE-2022-23521

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/git/+bug/2003204/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1] Re: Microsoft has a majority market share

[Eliah Kagan]

** Information type changed from Public Security to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1

Title:
  Microsoft has a majority market share

To manage notifications about this bug go to:
https://bugs.launchpad.net/clubdistro/+bug/1/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734702] Re: perldoc shows lots of escapes

[Eliah Kagan]

This bug affects my Lubuntu 17.10 (64-bit) system, which has version
5.26.0-8ubuntu1 of the perl and perl-doc packages. I noticed the bug
immediately upon checking for it after Zanna (https://launchpad.net
/~rose-anna-bleasdale / https://askubuntu.com/users/527764/zanna)
reported experiencing it in Ubuntu MATE 17.10. Until this bug is fixed,
I suggest the workaround of setting the PAGER environment variable to
"less" so that the proper configuration for less is used; other full
workarounds are also effective (see below).

The problem does not appear to depend in any way on what sort of
terminal emulator is used. I tried in LXTerminal (TERM=xterm), XTerm
(TERM=xterm), a virtual console (TERM=linux), and via SSH (TERM=xterm).
Zanna tried in MATE Terminal (TERM=xterm), GNOME Terminal (TERM=xterm-
256color), Konsole (TERM=xterm-256color), Tilda (TERM=xterm-256color),
XTerm (TERM=xterm), and a virtual console (TERM=linux). See
https://chat.stackexchange.com/transcript/message/42130009#42130009 and
subsequent messages for details. It occurred for us both no matter what
terminals we used. I believe this is the same bug as reported here.

In case it is helpful, I have attached a file showing the debugging
output produced by running "perldoc -D perlsyn" on my Lubuntu 17.10
system. Note the presence of this line:

About to call Pod::Perldoc::ToTerm->pager_configuration("/usr/bin
/sensible-pager")

I suspect that the problem is that the necessary configuration for less
to permit terminal escape sequences--specifically, that the -R option
either be passed to it or present in the LESS environment variable--is
not satisfied when the pager configuration for sensible-pager is used,
even when sensible-pager runs less, as it does by default in Ubuntu.

I further suspect that many, or perhaps all, 17.10 systems have this bug
in their default configuration (though it would only be noticed if users
install and run perldoc). This strongly resembles
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735134. This bug may
be considered a regression, in that the problem had previously occurred
and was then prevented by the addition of this code in Perldoc.pm, which
is present in 16.04 but removed in 17.10 (see below for details):

# fix visible escape codes in ToTerm output
# https://bugs.debian.org/758689
local $ENV{LESS} = defined $ENV{LESS} ? "$ENV{LESS} -R" : "-R";

The simplest workaround for this bug that I am aware of is to pass the
-t flag to perldoc. As in the workaround described in the bug report
here, the resulting formatting is readable but not as fancy as usual.

A *full* workaround is also possible, and is only slightly more
complicated. Telling perldoc explicitly that you want "less" by defining
the PAGER environment variable works:

PAGER=less perldoc perlsyn

Otherwise, it finds sensible-pager first (see above), and appears not to
place -R in LESS (see below), because it does not know that the
sensible-pager shell script runs less.

The problem may also be avoided by ensuring that an environment variable
with the name LESS and a value that specifies the R option is present.
For example, this works:

LESS=-R perldoc perlsyn

Or this may be preferred, because if you have a LESS environment
variable with other options, they will still be used (and if not, it has
the same effect as above):

LESS="$LESS -R" perldoc perlsyn

Or you can pipe to less and pass -R:

perldoc perlsyn | less -R

If these workarounds do not work for you (i.e., for the original author
of this bug report), then I might be mistaken in my belief that the bug
I am experiencing is the same as yours.

This bug does not appear to affect Ubuntu 16.04 LTS. It does not happen
on my Lubuntu 16.04 LTS (64-bit) system. Ubuntu 16.04 LTS has
"/usr/share/perl/5.22/Pod/Perldoc.pm" which uses this loop to open the
document in a pager:

foreach my $pager (@pagers) {
$self->aside("About to try calling $pager $output\n");
if ($self->is_vms) {
last if system("$pager $output") == 0;
} else {
# fix visible escape codes in ToTerm output
# bugs.debian.org/758689
local $ENV{LESS} = defined $ENV{LESS} ? "$ENV{LESS} -R" : "-R";
last if system("$pager \"$output\"") == 0;
}
}

Ubuntu 17.10 has this corresponding loop, which no longer directly
attempts to modify the LESS environment variable in order to prevent
Debian Bug 758689 from occurring:

foreach my $pager (@pagers) {
$self->aside("About to try calling $pager $output\n");
if ($self->is_vms) {
last if system("$pager $output") == 0;
} elsif($self->is_amigaos) {
last if system($pager, $output) == 0;
} else {
my $formatter = $self->{'formatter_class'};
if ( $formatter->can('pager_configuration') ) {
$self->aside("About to call $formatter" . 
"->pager_configuration(\"$pager\")\n");

[Bug 1539995] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

[Eliah Kagan]

This apparently has not gone away; I got it on Artful. There are some
details in duplicate bug 1707854.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1539995

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1539995/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707854] Re: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

[Eliah Kagan]

*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995

This bug report is for the bug in apport or GTK+, *not* for the kernel
bug (if any) that triggered it. However, in case the kernel oops that
triggered the apport-gtk instance that crashed is relevant, here's the
output of dmesg.

** Attachment added: "output of dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1707854/+attachment/4925074/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707854

Title:
  apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1707854/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707854] [NEW] apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()

[Eliah Kagan]

*** This bug is a duplicate of bug 1539995 ***
https://bugs.launchpad.net/bugs/1539995

Public bug reported:

On an Xubuntu Artful amd64 system with linux-generic 4.11.0.12.12,
libgtk-3-0 3.22.17-0ubuntu1, and apport-gtk 2.20.6-0ubuntu4, I viewed
the details on a kernel crash report prepared by apport-gtk titled "NMI
watchdog: BUG: soft lockup - CPU#0 stuck for 24s! [kworker/0:0:2661]"
but decided not to report that bug. This is a VMware Workstation 12.5.7
virtual machine that I believe incurs slowdowns from the host from time
to time. After I successfully quit the Apport dialog box that would
allow me to report the bug, an unexpected smaller window appeared with
no contents and "Ubuntu" (without the quotes) as its title. I waited
several minutes but no window contents appeared.

This all actually occurred twice at a time -- apparently there were two
kernel soft locks at different times, and Apport offered to report bugs
relating to both events. I clicked through to view the details on both.
I quit both dialog boxes and got two smaller windows with no contents;
these windows never changed. I did not take a screenshot of the windows,
but I did use xwininfo to obtain the window ID of one of them and then
the xprop command to obtain information about it, following the
technique described at https://unix.stackexchange.com/a/84981. The
output of "xprop -id 0x42011b1" is attached as xprop.txt.

Then I closed the two windows by clicking the X. My window manager told
me one of them was not responding and asked if I wanted to force it to
close, which I did. After this, at least one of the two instances of
apport-gtk apparently segfaulted; another apport window, which appeared
to work correctly, eventually came up to help me report the crash as a
bug, which I am doing now. I don't know for sure that the crash is
actually from when I forced the window to close, or from before that; it
could even have happened before the two mysterious windows were created.
Furthermore, I don't know if the window I ran xprop to get information
about came from the same instance of apport-gtk that crashed, or from
the other instance.

I don't know if this bug is in apport or some GTK+ package such as
libgtk-3-0. It resembles bug 1539995, which is considered to be a GTK+
bug rather than an apport bug and, as of this writing, appears (along
with its duplicates) not known to affect any releases except Xenial and
Yakkety. (Perhaps the forthcoming symbolic retrace will shed light on
the similarity.)

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: apport-gtk 2.20.6-0ubuntu4
ProcVersionSignature: Ubuntu 4.11.0-12.18-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Tue Aug  1 02:34:38 2017
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f789c06ea78 :   
mov(%r14),%rax
 PC (0x7f789c06ea78) ok
 source "(%r14)" (0x) not located in a known VMA region (needed 
readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: apport
StacktraceTop:
 gtk_widget_translate_coordinates () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_event_controller_handle_event () from 
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGSEGV in gtk_widget_translate_coordinates()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful

** Attachment added: "output of "xprop -id 0x42011b1"; 0x42011b1 was the ID of 
one of the mysterious windows"
   https://bugs.launchpad.net/bugs/1707854/+attachment/4925061/+files/xprop.txt

** Information type changed from Private to Public

** Description changed:

- On an Xubuntu Artful amd64 system with libgtk-3-0 3.22.17-0ubuntu1 and
- apport-gtk 2.20.6-0ubuntu4, I viewed the details on a kernel crash
- report prepared by apport-gtk titled "NMI watchdog: BUG: soft lockup -
- CPU#0 stuck for 24s! [kworker/0:0:2661]" but decided not to report that
- bug. This is a VMware Workstation 12.5.7 virtual machine that I believe
- incurs slowdowns from the host from time to time. After I successfully
- quit the Apport dialog box that would allow me to report the bug, an
- unexpected smaller window appeared with no contents and "Ubuntu"
- (without the quotes) as its title. I waited several minutes but no
- window 

[Bug 1707829] [NEW] systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

[Eliah Kagan]

*** This bug is a duplicate of bug 1605307 ***
https://bugs.launchpad.net/bugs/1605307

Public bug reported:

Apport told me systemd-resolved crashed when I logged in to my fully
updated Xubuntu Artful amd64 system. This is the same virtual machine
for which I reported bug 1707792 earlier today; potentially relevant
details about the system installed on this machine may be found in that
bug report.

I suspect this is still bug 1707792 (which is a duplicate of bug
1705870), but this also resembles bug 1605307, which was originally
reported against Yakkety but has since also been tagged Zesty and
Artful. Are these all really the same bug?

After the symbolic retrace and depending on what it shows, I will likely
mark this as a duplicate of something else, if that is not done
automatically.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Jul 31 22:16:39 2017
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-resolved
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 sd_event_wait () from /lib/systemd/libsystemd-shared-234.so
 sd_event_run () from /lib/systemd/libsystemd-shared-234.so
 sd_event_loop () from /lib/systemd/libsystemd-shared-234.so
 ?? ()
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 3 overridden configuration files found.
Title: systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful package-from-proposed

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707829

Title:
  systemd-resolved crashed with SIGABRT in __epoll_wait_nocancel()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707829/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Eliah Kagan]

*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

** Description changed:

  I don't know if this should be considered a bug in systemd or apport.
  
  systemd-udevd appears to crash with this bug on each boot. This is a
  fully updated Xubuntu Artful amd64 system (installed yesterday from the
  daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport
- 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no
- swap and runs inside a VMware Workstation 12.5.7 virtual machine (with
- open-vm-tools) on a Windows host. The host system has not approached
- memory exhaustion. I suspect these details may be relevant, because the
- host system sometimes experiences unexplained slowdowns when I/O is
- high. Note that I only suspect, and do not actually know for sure, that
- this bug may have been triggered by the host system's I/O problems.
+ 2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system swaps
+ to a 948 MiB swap file (/swapfile) and runs inside a VMware Workstation
+ 12.5.7 virtual machine (with open-vm-tools) on a Windows host. The host
+ system has not approached memory exhaustion. I suspect these details may
+ be relevant, because the host system sometimes experiences unexplained
+ slowdowns when I/O is high. Note that I only suspect, and do not
+ actually know for sure, that this bug may have been triggered by the
+ host system's I/O problems.
  
  I only know about this crash because Apport notified me. Starting the
  system seems to take longer than it should; specifically, once the non-
  graphical login prompt is shown, it sometimes takes up to a minute for
  LightDM to appear. But I don't know if that is related, and beyond that,
  I have not observed anything going wrong on the system. When I
  originally installed this Ubuntu (guest) system, Apport did not inform
  me of a crash. Since then, the host system engaged in more intensive
  I/O, and also I enabled artful-proposed, and now the crash occurs. I
  don't know if either of these changes are relevant.
  
  This most resembles bug 1705870, which occurred in Artful with some
  slightly earlier package versions. Depending on the results of the
  symbolic retrace, I might mark this as a duplicate of that bug. It also
  resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many)
  duplicates. That bug (i.e., bug 1433320) was considered to affect apport
  rather than systemd (see
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10)
  and is considered fixed. (To a lesser extent, this bug resembles bug
  1437896, which that bug mentions, and which is considered a bug in
  systemd.)
  
  I have made /bin/sh a symlink to bash on this system instead of dash
  (because I am using this system to test
  http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html,
  which expects it). Aside from making startup scripts run a bit slower
  and increasing memory footprint slightly, I suspect this is irrelevant
  to this bug, but it's a significant (and *unusual*) change so I figured
  it is worth mentioning.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
  Uname: Linux 4.11.0-12-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  Date: Mon Jul 31 17:41:49 2017
  ExecutablePath: /lib/systemd/systemd-udevd
  InstallationDate: Installed on 2017-07-31 (0 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcCmdline: /lib/systemd/systemd-udevd
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
   ?? ()
   ?? ()
   ?? ()
   __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291
  Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 

[Bug 1705870] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Eliah Kagan]

I've experienced this bug, also in a virtual machine (though with VMware
rather than QEMU). See bug 1707792 for details.

These bugs have a lot in common with bug 1433320, though that is
considered fixed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705870

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705870/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707792] Re: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Eliah Kagan]

*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

** Attachment removed: "the output of dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707792/+attachment/4924803/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1707792

Title:
  systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1707792] [NEW] systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()

[Eliah Kagan]

*** This bug is a duplicate of bug 1705870 ***
https://bugs.launchpad.net/bugs/1705870

Public bug reported:

I don't know if this should be considered a bug in systemd or apport.

systemd-udevd appears to crash with this bug on each boot. This is a
fully updated Xubuntu Artful amd64 system (installed yesterday from the
daily-live) with systemd 234-2ubuntu1, udev 234-2ubuntu1, apport
2.20.6-0ubuntu4, and kernel version 4.11.0-12-generic. The system has no
swap and runs inside a VMware Workstation 12.5.7 virtual machine (with
open-vm-tools) on a Windows host. The host system has not approached
memory exhaustion. I suspect these details may be relevant, because the
host system sometimes experiences unexplained slowdowns when I/O is
high. Note that I only suspect, and do not actually know for sure, that
this bug may have been triggered by the host system's I/O problems.

I only know about this crash because Apport notified me. Starting the
system seems to take longer than it should; specifically, once the non-
graphical login prompt is shown, it sometimes takes up to a minute for
LightDM to appear. But I don't know if that is related, and beyond that,
I have not observed anything going wrong on the system. When I
originally installed this Ubuntu (guest) system, Apport did not inform
me of a crash. Since then, the host system engaged in more intensive
I/O, and also I enabled artful-proposed, and now the crash occurs. I
don't know if either of these changes are relevant.

This most resembles bug 1705870, which occurred in Artful with some
slightly earlier package versions. Depending on the results of the
symbolic retrace, I might mark this as a duplicate of that bug. It also
resembles bug 1663995, bug 1506798, bug 1433320, and some of its (many)
duplicates. That bug (i.e., bug 1433320) was considered to affect apport
rather than systemd (see
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1433320/comments/10)
and is considered fixed. (To a lesser extent, this bug resembles bug
1437896, which that bug mentions, and which is considered a bug in
systemd.)

I have made /bin/sh a symlink to bash on this system instead of dash
(because I am using this system to test
http://www.linuxfromscratch.org/lfs/view/development/chapter02/mounting.html,
which expects it). Aside from making startup scripts run a bit slower
and increasing memory footprint slightly, I suspect this is irrelevant
to this bug, but it's a significant (and *unusual*) change so I figured
it is worth mentioning.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: udev 234-2ubuntu1
ProcVersionSignature: Ubuntu 4.11.0-12.17-generic 4.11.12
Uname: Linux 4.11.0-12-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
Date: Mon Jul 31 17:41:49 2017
ExecutablePath: /lib/systemd/systemd-udevd
InstallationDate: Installed on 2017-07-31 (0 days ago)
InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170731)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: /lib/systemd/systemd-udevd
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-12-generic 
root=UUID=3ebdfb0d-efad-4049-955f-56e299d1acea ro quiet splash
Signal: 6
SourcePackage: systemd
StacktraceTop:
 __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:84
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main (main=0x1f82c781c0, argc=1, argv=0x7ffddfff7de8, 
init=, fini=, rtld_fini=, 
stack_end=0x7ffddfff7dd8) at ../csu/libc-start.c:291
Title: systemd-udevd crashed with SIGABRT in __epoll_wait_nocancel()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/02/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful package-from-proposed

** Attachment added: "the output of dmesg"
   https://bugs.launchpad.net/bugs/1707792/+attachment/4924803/+files/dmesg.txt

** Information type changed from Private to Public

** Description changed:

  I don't know if this should be considered a bug in systemd or apport.
  
  systemd-udevd 

[Bug 1437966] [NEW] menu-cache-gen crashed with SIGSEGV in rawmemchr()

[Eliah Kagan]

Public bug reported:

I ran sudo do-release-upgrade -d on a Utopic amd64 system, to upgrade
it to Vivid Beta 2. I was informed menu-cache-gen crashed. The release
upgrade appears to be continuing without problems. If the upgrade fails
and I cannot rule this bug out as the cause, I will update this bug
report. Otherwise, hopefully the attached data (e.g., stack trace) will
document the bug sufficiently.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: libmenu-cache-bin 1.0.0-1
ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CurrentDesktop: LXDE
Date: Sun Mar 29 19:05:46 2015
ExecutablePath: /usr/lib/menu-cache/menu-cache-gen
InstallationDate: Installed on 2014-10-15 (165 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: /usr/lib/menu-cache/menu-cache-gen -l en_US -i applications.menu 
-o /home/username/.cache/menus/510f7aeb142993152432ddb6e4c92e8b
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f71caa2c51f rawmemchr+31:   movdqu (%rdi),%xmm0
 PC (0x7f71caa2c51f) ok
 source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
 destination %xmm0 ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: menu-cache
StacktraceTop:
 rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
 _IO_str_init_static_internal (sf=sf@entry=0x74edade0, ptr=ptr@entry=0x0, 
size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44
 __GI___isoc99_vsscanf (string=0x0, format=0x40ab5f %d.%u, 
args=args@entry=0x74edaf08) at isoc99_vsscanf.c:41
 __isoc99_sscanf (s=optimized out, format=optimized out) at 
isoc99_sscanf.c:31
 ?? ()
Title: menu-cache-gen crashed with SIGSEGV in rawmemchr()
UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: menu-cache (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace vivid

** Information type changed from Private to Public

** Description changed:

- I ran sudo do-release-upgrade -d on a Utopic amdt64 system, to upgrade
+ I ran sudo do-release-upgrade -d on a Utopic amd64 system, to upgrade
  it to Vivid Beta 2. I was informed menu-cache-gen crashed. The release
  upgrade appears to be continuing without problems. If the upgrade fails
  and I cannot rule this bug out as the cause, I will update this bug
  report. Otherwise, hopefully the attached data (e.g., stack trace) will
  document the bug sufficiently.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: libmenu-cache-bin 1.0.0-1
  ProcVersionSignature: Ubuntu 3.16.0-34.45-generic 3.16.7-ckt8
  Uname: Linux 3.16.0-34-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Sun Mar 29 19:05:46 2015
  ExecutablePath: /usr/lib/menu-cache/menu-cache-gen
  InstallationDate: Installed on 2014-10-15 (165 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
  ProcCmdline: /usr/lib/menu-cache/menu-cache-gen -l en_US -i applications.menu 
-o /home/username/.cache/menus/510f7aeb142993152432ddb6e4c92e8b
  ProcEnviron:
-  LANGUAGE=en_US
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_US
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SegvAnalysis:
-  Segfault happened at: 0x7f71caa2c51f rawmemchr+31: movdqu (%rdi),%xmm0
-  PC (0x7f71caa2c51f) ok
-  source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
-  destination %xmm0 ok
+  Segfault happened at: 0x7f71caa2c51f rawmemchr+31: movdqu (%rdi),%xmm0
+  PC (0x7f71caa2c51f) ok
+  source (%rdi) (0x) not located in a known VMA region (needed 
readable region)!
+  destination %xmm0 ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: menu-cache
  StacktraceTop:
-  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
-  _IO_str_init_static_internal (sf=sf@entry=0x74edade0, ptr=ptr@entry=0x0, 
size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44
-  __GI___isoc99_vsscanf (string=0x0, format=0x40ab5f %d.%u, 
args=args@entry=0x74edaf08) at isoc99_vsscanf.c:41
-  __isoc99_sscanf (s=optimized out, format=optimized out) at 
isoc99_sscanf.c:31
-  ?? ()
+  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
+  _IO_str_init_static_internal (sf=sf@entry=0x74edade0, ptr=ptr@entry=0x0, 
size=size@entry=0, pstart=pstart@entry=0x0) at strops.c:44
+  __GI___isoc99_vsscanf (string=0x0, format=0x40ab5f %d.%u, 
args=args@entry=0x74edaf08) at isoc99_vsscanf.c:41
+  __isoc99_sscanf (s=optimized out, format=optimized out) at 
isoc99_sscanf.c:31
+  ?? ()
  Title: menu-cache-gen crashed with SIGSEGV in rawmemchr()
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days 

[Bug 1436499] [NEW] vlc crashed with SIGSEGV in varcmp()

[Eliah Kagan]

Public bug reported:

I successfully imported a large music library (~310 GiB in ~64000 files)
into vlc 2.2.0~pre2-4build1 on a Lubuntu Utopic amd64 system, listened
to music for a while, left and returned to my machine a couple hours
later, closed vlc, reopened it (seeing that my imported music was still
listed), then closed it again. At some point after I got back to my
machine, vlc crashed, but I don't know when since the only reason I know
a crash happened was that Apport told me. I suspect the crash occurred
when I closed vlc the second time, though it may have been when I closed
vlc the first time, or at some other point.

Hopefully the automatically attached stack trace will provide useful
information.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: vlc-nox 2.2.0~pre2-4build1
ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Mar 25 13:51:18 2015
ExecutablePath: /usr/bin/vlc
InstallationDate: Installed on 2014-10-15 (161 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: /usr/bin/vlc --started-from-file
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcf159e75d0 varcmp: mov(%rsi),%rsi
 PC (0x7fcf159e75d0) ok
 source (%rsi) (0x0004) not located in a known VMA region (needed 
readable region)!
 destination %rsi ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: vlc
StacktraceTop:
 varcmp (a=0x7fcee9f90d30, b=0x4) at misc/variables.c:145
 __tfind (key=key@entry=0x7fcee9f90d30, vrootp=vrootp@entry=0x1be5cd8, 
compar=compar@entry=0x7fcf159e75d0 varcmp) at tsearch.c:320
 Lookup (psz_name=0x7fcf15a0d5cb item-change, obj=0x1be5d68) at 
misc/variables.c:154
 var_SetChecked (p_this=0x1be5d68, psz_name=psz_name@entry=0x7fcf15a0d5cb 
item-change, expected_type=expected_type@entry=112, val=...) at 
misc/variables.c:712
 var_SetAddress (ptr=optimized out, psz_name=0x7fcf15a0d5cb item-change, 
p_obj=optimized out) at ../include/vlc_variables.h:287
Title: vlc crashed with SIGSEGV in varcmp()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: vlc (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1436499

Title:
  vlc crashed with SIGSEGV in varcmp()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1436499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1430295] [NEW] lxpanel crashed with SIGABRT in start_thread()

[Eliah Kagan]

*** This bug is a duplicate of bug 1222191 ***
https://bugs.launchpad.net/bugs/1222191

Public bug reported:

lxpanel crashed on login on a Lubuntu Utopic amd64 system. It then
appears to have launched again without problems. Graphical login
appeared to take slightly longer than usual but that is the only sign of
the crash that I was able to see, besides Apport informing me it had
occurred.

This has a superficial similarity to
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/549198, though I
do not think they are the same bug. They terminated with different
signals, they appear to have been triggered differently, and there is
not much stack trace information there (even in the symbolic retrace) so
it might be hard ever to know for sure if they arise from the same
problem. In any case, if this does turn out to be the same bug it should
still probably not be made a duplicate of that bug, as per
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/549198/comments/2.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: lxpanel 0.6.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-32.42-generic 3.16.7-ckt7
Uname: Linux 3.16.0-32-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
Config_Home_Lubuntu:
 [Command]
 FileManager=lxsession-default filemanager
 Terminal=lxsession-default terminal
 Logout=lxsession-default quit
CurrentDesktop: LXDE
Date: Mon Mar  9 21:32:12 2015
ExecutablePath: /usr/bin/lxpanel
InstallationDate: Installed on 2014-10-15 (145 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: lxpanel --profile Lubuntu
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: lxpanel
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmenu-cache.so.3
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7fe70a941700) at pthread_create.c:309
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: lxpanel crashed with SIGABRT in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: lxpanel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1430295

Title:
  lxpanel crashed with SIGABRT in start_thread()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1430295/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1386239] [NEW] lxpanel crashed with SIGABRT in start_thread()

[Eliah Kagan]

Public bug reported:

On a Lubuntu Utopic amd64 system (fully up to date as of a few hours
ago), lxpanel 0.6.2-0ubuntu2 crashed on login. Before the crash--or
possibly as Apport was beginning to collect information before first
prompting me--the top panel was visible, but blank. During this time,
notifications appeared to work: I received a notification about not
being connected to a network. (My network connection status was not part
of the problem.)

After the crash, lxpanel relaunched automatically, without any action on
my part. The relaunched lxpanel seems to be working fine.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: lxpanel 0.6.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Config_Home_Lubuntu:
 [Command]
 FileManager=lxsession-default filemanager
 Terminal=lxsession-default terminal
 Logout=lxsession-default quit
CurrentDesktop: LXDE
Date: Mon Oct 27 10:40:28 2014
ExecutablePath: /usr/bin/lxpanel
InstallationDate: Installed on 2014-10-15 (11 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: lxpanel --profile Lubuntu
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: lxpanel
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmenu-cache.so.3
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 start_thread (arg=0x7f74a6c96700) at pthread_create.c:309
 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
Title: lxpanel crashed with SIGABRT in start_thread()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: lxpanel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386239

Title:
  lxpanel crashed with SIGABRT in start_thread()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxpanel/+bug/1386239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1386253] Re: abiword crashed with SIGABRT in AP_TopRuler::mousePress()

[Eliah Kagan]

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386253

Title:
  abiword crashed with SIGABRT in AP_TopRuler::mousePress()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1386253/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1385570] [NEW] chromium-browser crashed with SIGSEGV in gpu::gles2::GLES2DecoderImpl::Initialize()

[Eliah Kagan]

*** This bug is a duplicate of bug 1378627 ***
https://bugs.launchpad.net/bugs/1378627

Public bug reported:

chromium-browser 37.0.2062.94-0ubuntu1~pkg1065 on Lubuntu Utopic amd64
sometimes crashes on launch. This happens at least daily, but somewhat
less than half the time the browser is launched. Following the crash and
without deliberately relaunching the application, Chromium usually still
seems to work (but Chromium uses multiple processes, so that is not
surprising). This is on a laptop with Intel i915 onboard video.

When I launch Chromium, both in cases when a crash occurs and in cases
when there is no crash, the Chromium window remains undrawn for a while
(perhaps half a minute), showing whatever was last drawn behind it. This
is confusing because it looks like other windows or the desktop are in
the foreground and could be interacted with, when actually they are not
--however, that is not the bug I am reporting here. Rather, I mention it
in case it is related to the crash (since it looks like the crash may be
related to OpenGL rendering).

In case it's relevant, the output of sudo lshw -C video is:

  *-display   
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics  Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:109 memory:d000-d03f memory:c000-cfff 
ioport:f080(size=8)

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 37.0.2062.94-0ubuntu1~pkg1065
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CrashCounter: 1
CurrentDesktop: LXDE
Date: Fri Oct 24 23:22:44 2014
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-10-15 (9 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=16578.0.637767605\ 
--supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15\ 
--disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ 
--gpu-device-id=0x0f31\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis:
 Segfault happened at: 0x7fea04d4c63f:  mov0x1f8(%rax),%r15
 PC (0x7fea04d4c63f) ok
 source 0x1f8(%rax) (0x01f8) not located in a known VMA region (needed 
readable region)!
 destination %r15 ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
Title: chromium-browser crashed with SIGSEGV in 
gpu::gles2::GLES2DecoderImpl::Initialize()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
modified.conffile..etc.default.chromium.browser: [deleted]
mtime.conffile..etc.chromium.browser.default: 2014-10-18T02:01:31.797924

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1385570

Title:
  chromium-browser crashed with SIGSEGV in
  gpu::gles2::GLES2DecoderImpl::Initialize()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1385570/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1384557] [NEW] gpartedbin crashed with SIGSEGV

[Eliah Kagan]

Public bug reported:

On a Lubuntu Utopic amd64 system, gparted 0.19.0-1build1 crashed when I
created a new partition table (of type Apple Partition Map) on a 16 GB
(~15 GiB) USB flash drive, selecting mac (as this type is called in
the GParted interface).

The new partition table was apparently successfully created before the
crash. When I ran GParted again (same version, relaunching immediately
after the crash), it recognized it. I was able to create it again on the
same device, also successfully but this time with no crash. I had also
previously created a mac partition table on this USB stick with
GParted, on this machine, that time with no crashes. I don't know for
sure if the version of GParted I'd used before was the same.

I was then able to make a 16 GB (~15 GiB) HFS+ partition in GParted--
both previously, and this time.

Between the original, error-free operations and the partition table
creation operation that succeeded but triggered a crash, I had
reformatted this USB stick, also with an Apple Partition Map partition
table, but with two 8 GB HFS+ partitions with journalling enabled. I did
that on an old Mac OS X 10.4 Tiger system (running on a PowerMac G5). I
don't know if something about the new layout triggered the crash, or
not.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: gparted 0.19.0-1build1
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Thu Oct 23 02:33:15 2014
Disassembly: = 0x7f36: Cannot access memory at address 0x7f36
ExecutablePath: /usr/sbin/gpartedbin
InstallationDate: Installed on 2014-10-15 (7 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141014)
ProcCmdline: /usr/sbin/gpartedbin
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f36:  Cannot access memory at address 
0x7f36
 PC (0x7f36) not located in a known VMA region (needed executable 
region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: gparted
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
Title: gpartedbin crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: gparted (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1384557

Title:
  gpartedbin crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1384557/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1377376] Re: mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

** Attachment added: dpkg.log
   
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+attachment/4224281/+files/dpkg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377376

Title:
  mate-display-properties crashed with SIGSEGV in
  g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1377376] [NEW] mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

Public bug reported:

On an Ubuntu MATE Utopic amd64 system in a VirtualBox VM with Guest
Additions 4.3.16_95972 installed, mate-display-properties (provided by
mate-control-center 1.8.2+dfsg1-1) crashed. I opened it up with System 
Preferences  Monitors, the application window displayed momentarily,
then disappeared. When I ran it again the same way, the crash did not
occur.

Some updates were being installed at the time of the crash (I was
running sudo apt-get upgrade), so perhaps that is related. mate-
display-properties was not one of the packages being updated. I'm
attaching possibly relevant information as term-veryshort.log (just some
relevant text copied from the terminal) and the usual APT and dpkg-
related log files.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: mate-control-center 1.8.2+dfsg1-1
ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3
Uname: Linux 3.16.0-20-generic x86_64
ApportVersion: 2.14.7-0ubuntu3
Architecture: amd64
Date: Sat Oct  4 00:29:58 2014
Disassembly: = 0x4:Cannot access memory at address 0x4
ExecutablePath: /usr/bin/mate-display-properties
InstallationDate: Installed on 2014-10-02 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - beta2 amd64 (20140925)
ProcCmdline: mate-display-properties
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4: Cannot access memory at address 0x4
 PC (0x0004) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: mate-control-center
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (mate-power-manager:4912): GLib-CRITICAL **: Source ID 90 was not found when 
attempting to remove it
 (mate-screensaver:4926): GLib-CRITICAL **: Source ID 23 was not found when 
attempting to remove it

** Affects: mate-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace utopic

** Attachment added: term-veryshort.log
   
https://bugs.launchpad.net/bugs/1377376/+attachment/4224271/+files/term-veryshort.log

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377376

Title:
  mate-display-properties crashed with SIGSEGV in
  g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1377376] Re: mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

** Attachment added: history.log
   
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+attachment/4224280/+files/history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377376

Title:
  mate-display-properties crashed with SIGSEGV in
  g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1377376] Re: mate-display-properties crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

** Attachment added: term.log
   
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+attachment/4224279/+files/term.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1377376

Title:
  mate-display-properties crashed with SIGSEGV in
  g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-control-center/+bug/1377376/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1366653] Re: kernel BUG at /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

[Eliah Kagan]

Embarrassingly, I wrote Ubuntu Mint in the bug report (there is no
such OS but some people use that term to mean Linux Mint. Rather, I
had this bug on Ubuntu MATE Utopic, not Linux Mint. It may also exist on
Mint but I have not verified this. I apologize for the wrong information
I gave in my bug report.

I'm editing the report and changing the distro/package back to open-vm-
tools (Ubuntu), but if there's an independent reason to believe this
affects other distros/projects, then by all means anyone may feel free
to make any further appropriate changes.

** Description changed:

- A kernel panic occurred while shutting down an Ubuntu Mint (Utopic)
+ A kernel panic occurred while shutting down an Ubuntu MATE (Utopic)
  amd64 system running in a VMware Workstation 10.0.3 build-1895310
  virtual machine with VMware Tools installed. Messages appeared to
  indicate a problem in one of the vmware kernel modules as the cause.
  Details collected by apport appeared that they may be sufficient to
  identify the cause specifically. I hope so, since I don't have any
  information about any actions I may have taken to trigger this panic (or
  to have prevented it in the past).
  
  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-13-generic 3.16.0-13.19
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-13-generic x86_64
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ek 2627 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ek 2627 F pulseaudio
  Date: Sun Sep  7 20:43:26 2014
  Failure: oops
  HibernationDevice: RESUME=UUID=03575561-2dfc-4d93-a9e9-d4d5a3f06f84
  InstallationDate: Installed on 2014-08-19 (19 days ago)
  InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
  IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
-  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
-  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=6b980efc-3cb1-4f6e-9705-9c4fdd083560 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Project changed: linuxmint = ubuntu-mate

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1366653

Title:
  kernel BUG at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1366653/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1366653] Re: kernel BUG at /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

[Eliah Kagan]

Embarrassingly, I wrote Ubuntu Mint in the bug report (there is no
such OS but some people use that term to mean Linux Mint). Rather, I
had this bug on Ubuntu MATE Utopic, not Linux Mint. It may also exist on
Mint but I have not verified this. I apologize for the wrong information
I gave in my bug report.

I've edited the report and changing the distro/package back to open-vm-
tools (Ubuntu), but if there's an independent reason to believe this
affects other distros/projects, then by all means anyone may feel free
to make any further appropriate changes.

I'm pretty sure it is correct for this to be filed against open-vm-tools
in Ubuntu. I'm less sure Ubuntu MATE needs to be listed, but since I
believe all changes made since I filed the report were a result of my
incorrect description, I've set it back to that and it can be modified
further by others as needed.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to open-vm-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1366653

Title:
  kernel BUG at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1366653/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1366653] Re: kernel BUG at /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

[Eliah Kagan]

Embarrassingly, I wrote Ubuntu Mint in the bug report (there is no
such OS but some people use that term to mean Linux Mint. Rather, I
had this bug on Ubuntu MATE Utopic, not Linux Mint. It may also exist on
Mint but I have not verified this. I apologize for the wrong information
I gave in my bug report.

I'm editing the report and changing the distro/package back to open-vm-
tools (Ubuntu), but if there's an independent reason to believe this
affects other distros/projects, then by all means anyone may feel free
to make any further appropriate changes.

** Description changed:

- A kernel panic occurred while shutting down an Ubuntu Mint (Utopic)
+ A kernel panic occurred while shutting down an Ubuntu MATE (Utopic)
  amd64 system running in a VMware Workstation 10.0.3 build-1895310
  virtual machine with VMware Tools installed. Messages appeared to
  indicate a problem in one of the vmware kernel modules as the cause.
  Details collected by apport appeared that they may be sufficient to
  identify the cause specifically. I hope so, since I don't have any
  information about any actions I may have taken to trigger this panic (or
  to have prevented it in the past).
  
  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-13-generic 3.16.0-13.19
  ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
  Uname: Linux 3.16.0-13-generic x86_64
  Annotation: Your system might become unstablenow and might need to be 
restarted.
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  ek 2627 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ek 2627 F pulseaudio
  Date: Sun Sep  7 20:43:26 2014
  Failure: oops
  HibernationDevice: RESUME=UUID=03575561-2dfc-4d93-a9e9-d4d5a3f06f84
  InstallationDate: Installed on 2014-08-19 (19 days ago)
  InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
  IwConfig:
-  eth0  no wireless extensions.
-  
-  lono wireless extensions.
+  eth0  no wireless extensions.
+ 
+  lono wireless extensions.
  Lsusb:
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-  Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
-  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
-  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
-  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
+  Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
+  Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=6b980efc-3cb1-4f6e-9705-9c4fdd083560 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
  RfKill:
-  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  0: hci0: Bluetooth
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  Title: kernel BUG at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

** Also affects: open-vm-tools (Ubuntu)
   Importance: Undecided
   Status: New

** Project changed: linuxmint = ubuntu-mate

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366653

Title:
  kernel BUG at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1366653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1366653] Re: kernel BUG at /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

[Eliah Kagan]

Embarrassingly, I wrote Ubuntu Mint in the bug report (there is no
such OS but some people use that term to mean Linux Mint). Rather, I
had this bug on Ubuntu MATE Utopic, not Linux Mint. It may also exist on
Mint but I have not verified this. I apologize for the wrong information
I gave in my bug report.

I've edited the report and changing the distro/package back to open-vm-
tools (Ubuntu), but if there's an independent reason to believe this
affects other distros/projects, then by all means anyone may feel free
to make any further appropriate changes.

I'm pretty sure it is correct for this to be filed against open-vm-tools
in Ubuntu. I'm less sure Ubuntu MATE needs to be listed, but since I
believe all changes made since I filed the report were a result of my
incorrect description, I've set it back to that and it can be modified
further by others as needed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366653

Title:
  kernel BUG at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1366653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1366653] [NEW] kernel BUG at /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

[Eliah Kagan]

Public bug reported:

A kernel panic occurred while shutting down an Ubuntu Mint (Utopic)
amd64 system running in a VMware Workstation 10.0.3 build-1895310
virtual machine with VMware Tools installed. Messages appeared to
indicate a problem in one of the vmware kernel modules as the cause.
Details collected by apport appeared that they may be sufficient to
identify the cause specifically. I hope so, since I don't have any
information about any actions I may have taken to trigger this panic (or
to have prevented it in the past).

ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-13-generic 3.16.0-13.19
ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2
Uname: Linux 3.16.0-13-generic x86_64
Annotation: Your system might become unstablenow and might need to be restarted.
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ek 2627 F pulseaudio
Date: Sun Sep  7 20:43:26 2014
Failure: oops
HibernationDevice: RESUME=UUID=03575561-2dfc-4d93-a9e9-d4d5a3f06f84
InstallationDate: Installed on 2014-08-19 (19 days ago)
InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. 
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic 
root=UUID=6b980efc-3cb1-4f6e-9705-9c4fdd083560 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: kernel BUG at 
/build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2013
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-kerneloops kernel-driver-vmwgfx kernel-oops utopic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1366653

Title:
  kernel BUG at
  /build/buildd/linux-3.16.0/drivers/gpu/drm/vmwgfx/vmwgfx_drv.c:1187!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1366653/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1365232] [NEW] Xorg crashed (logging out and back in)

[Eliah Kagan]

Public bug reported:

Xorg (xserver-xorg 1:7.7+1ubuntu8) crashed on an Ubuntu MATE (Utopic)
amd64 system. Apport informed me of the crash when I logged in. I had
just logged out and back in.

At the time I was using this system to verify the correct behavior of
pam_env.so against another system on which it is not working. I had set
unimportant environment variables (FOO and BAR) in ~/.pam_environment,
changed them, and removed the file (which was otherwise empty). I did
this across a few graphical sessions, all within a few minutes of one
another.

I suspect that is not what triggered this crash but I'm not sure.

Recently I have some kernel messages which may or may not be related to
whatever triggered this crash:

[  853.112643] systemd-logind[1038]: New session c10 of user lightdm.
[  858.538808] init: tty1 main process ended, respawning
[  858.554498] systemd-logind[1038]: Failed to abandon scope session-c2.scope
[  858.554583] systemd-logind[1038]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc2_2escope
[ 1118.816570] systemd-logind[1038]: Failed to abandon scope session-c10.scope
[ 1118.816582] systemd-logind[1038]: Failed to abandon session scope: No such 
interface 'org.freedesktop.systemd1.Scope' on object at path 
/org/freedesktop/systemd1/unit/session_2dc10_2escope
[ 1118.826320] systemd-logind[1038]: New session c11 of user ek.
[ 1689.808829] audit: type=1400 audit(1409798550.085:26): apparmor=STATUS 
operation=profile_replace profile=unconfined 
name=/usr/lib/cups/backend/cups-pdf pid=6369 comm=apparmor_parser
[ 1689.808841] audit: type=1400 audit(1409798550.085:27): apparmor=STATUS 
operation=profile_replace profile=unconfined name=/usr/sbin/cupsd 
pid=6369 comm=apparmor_parser

I've attached the full output of 'dmesg' (dmesg.txt).

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-core 2:1.15.1-0ubuntu9
ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1
Uname: Linux 3.16.0-12-generic x86_64
ApportVersion: 2.14.7-0ubuntu1
Architecture: amd64
Date: Wed Sep  3 22:28:32 2014
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2014-08-19 (15 days ago)
InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
ProcEnviron:
 
Signal: 6
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: xorg-server (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash utopic

** Attachment added: output of dmesg
   https://bugs.launchpad.net/bugs/1365232/+attachment/4194916/+files/dmesg.txt

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365232

Title:
  Xorg crashed (logging out and back in)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1365232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1364217] [NEW] smbd -F crashed on Samba server configured through caja-share

[Eliah Kagan]

Public bug reported:

I'm not sure what triggered this crash; I would not have known there was
one if Apport hadn't caught it.

smbd -F (which I did not run manually) crashed on a Utopic i386 system
running the MATE desktop environment, through which the Samba server had
been automatically configured via Caja (with caja-share).

I was also unable to make shares of external volumes accessible (tested
with both a Windows and an Ubuntu client), but I am unsure if that is a
bug and my intention here is to report the crash, and not that problem
(unless they turn out to be facets of the same problem).

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: samba 2:4.1.11+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic i686
ApportVersion: 2.14.7-0ubuntu1
Architecture: i386
BothFailedConnect: Yes
CrashCounter: 1
Date: Mon Sep  1 23:55:42 2014
ExecutablePath: /usr/sbin/smbd
InstallationDate: Installed on 2014-08-13 (19 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140812)
NmbdLog:
 
ProcCmdline: smbd -F
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SambaServerRegression: Yes
Signal: 6
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: samba (Ubuntu)
 Importance: Medium
 Status: New


** Tags: apport-crash i386 utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1364217

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1364217] [NEW] smbd -F crashed on Samba server configured through caja-share

[Eliah Kagan]

Public bug reported:

I'm not sure what triggered this crash; I would not have known there was
one if Apport hadn't caught it.

smbd -F (which I did not run manually) crashed on a Utopic i386 system
running the MATE desktop environment, through which the Samba server had
been automatically configured via Caja (with caja-share).

I was also unable to make shares of external volumes accessible (tested
with both a Windows and an Ubuntu client), but I am unsure if that is a
bug and my intention here is to report the crash, and not that problem
(unless they turn out to be facets of the same problem).

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: samba 2:4.1.11+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic i686
ApportVersion: 2.14.7-0ubuntu1
Architecture: i386
BothFailedConnect: Yes
CrashCounter: 1
Date: Mon Sep  1 23:55:42 2014
ExecutablePath: /usr/sbin/smbd
InstallationDate: Installed on 2014-08-13 (19 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140812)
NmbdLog:
 
ProcCmdline: smbd -F
ProcEnviron:
 PATH=(custom, no user)
 TERM=linux
SambaServerRegression: Yes
Signal: 6
SmbConfIncluded: Yes
SmbLog:
 
SourcePackage: samba
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: samba (Ubuntu)
 Importance: Medium
 Status: New


** Tags: apport-crash i386 utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1364217

Title:
  smbd -F crashed on Samba server configured through caja-share

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1364217/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1359308] [NEW] mate-panel crashed when using window list

[Eliah Kagan]

Public bug reported:

On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2 crashed
when I clicked on an item in the window list (located in the bottom
panel). The panel reappeared and continued working correctly. This
happened while apt-get was upgrading packages, but mate-panel was not
one of the packages being upgraded.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: mate-panel 1.8.0+dfsg1-2
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
Date: Wed Aug 20 13:21:43 2014
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2014-08-19 (1 days ago)
InstallationMedia: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
ProcCmdline: mate-panel
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: mate-panel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: mate-panel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash apport-failed-retrace utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359308

Title:
  mate-panel crashed when using window list

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/1359308/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1358841] [NEW] mate-display-properties crashed (settings successfully changed)

[Eliah Kagan]

Public bug reported:

I booted the 64-bit Ubuntu Mate Alpha 2 desktop live image (ubuntu-
mate-14.10-alpha2-desktop-amd64.iso)--which has mate-control-center
1.8.1+dfsg1-4--on a virtual machine created and run in VMware
Workstation 10.0.3 build-1895310. I selected Try Ubuntu, and when the
desktop came up, I went to System  Preferences  Monitors and
successfully changed the resolution from 800x600 to 1440x900. Several
seconds later, I re-entered the Monitor Preferences (by accessing it
from the MATE menu in the same way as before) and clicked Make Default,
which appeared to succeed.

It showed my monitor as Unknown but I doubt that is a contributing
factor for this crash. I would not have known about this crash if Apport
had not informed me--the Monitor Preferences utility appeared to work
correctly in every way. I don't know if the crash was from the first or
the second time I ran it, as the Apport window appeared perhaps 30-60
seconds after the second run.

My understanding from previous experiences (without crashes) is that for
Monitor Preferences to exit automatically after the resolution is
successfully changed (which is what seemed to me to have occurred here)
is its normal behavior, and is not considered a bug nor typically caused
by a crash.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: mate-control-center 1.8.1+dfsg1-4
ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
Uname: Linux 3.16.0-6-generic x86_64
ApportVersion: 2.14.5-0ubuntu1
Architecture: amd64
CasperVersion: 1.340build1
Date: Tue Aug 19 16:27:09 2014
ExecutablePath: /usr/bin/mate-display-properties
LiveMediaBuild: Ubuntu MATE 14.10 Utopic Unicorn - Alpha amd64 (20140731)
ProcCmdline: mate-display-properties
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field Disassembly
Signal: 11
SourcePackage: mate-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: ubuntu-mate
 Importance: Undecided
 Status: New

** Affects: mate-control-center (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-crash utopic

** Information type changed from Private to Public

** Also affects: ubuntu-mate
   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/1358841

Title:
  mate-display-properties crashed (settings successfully changed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1358841/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1358400] [NEW] lxsession-default-apps crashed

[Eliah Kagan]

Public bug reported:

On Utopic i386 I unlocked my screen after a period of inactivity in the
MATE desktop (which I installed after installing Lubuntu Utopic) and was
informed that lxsession-default-apps (0.4.9.2+git20140410-0ubuntu2) had
crashed.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: lxsession-default-apps 0.4.9.2+git20140410-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
Uname: Linux 3.16.0-7-generic i686
ApportVersion: 2.14.5-0ubuntu4
Architecture: i386
Date: Sat Aug 16 11:24:59 2014
ExecutablePath: /usr/bin/lxsession-default-apps
InstallationDate: Installed on 2014-08-13 (5 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140812)
ProcCmdline: lxsession-default-apps
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: lxsession
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: lxsession (Ubuntu)
 Importance: Medium
 Status: New


** Tags: apport-crash i386 utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1358400

Title:
  lxsession-default-apps crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1358400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1356210] [NEW] chromium-browser often crashes on page open, including chrome://settings

[Eliah Kagan]

Public bug reported:

In chromium-browser 36.0.1985.125-0ubuntu2 on my Utopic i386 system
(fully up to date as of this report), some pages always cause the
browser to crash.

chrome://settings  is one of these pages (which makes effective browser
usage difficult).

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: chromium-browser 36.0.1985.125-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0
Uname: Linux 3.16.0-7-generic i686
ApportVersion: 2.14.5-0ubuntu4
Architecture: i386
Date: Wed Aug 13 03:05:35 2014
Desktop-Session:
 DESKTOP_SESSION = mate
 XDG_CONFIG_DIRS = /etc/xdg/xdg-mate:/etc/xdg
 XDG_DATA_DIRS = /usr/share/mate:/usr/local/share/:/usr/share/
DetectedPlugins:
 
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2014-08-13 (0 days ago)
InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha i386 (20140812)
ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=8579.0.674909058\ 
--supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,14,21\ 
--disable-accelerated-video-decode\ --gpu-vendor-id=0x1002\ 
--gpu-device-id=0x7149\ --gpu-driver-vendor\ --gpu-driver-versi
SegvAnalysis: Skipped: missing required field Disassembly
Signal: 11
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
 (process:8750): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
 (process:8898): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size 
== 0' failed
chromium-default: CHROMIUM_FLAGS=
gconf-keys: /desktop/gnome/applications/browser/exec = 
b''/desktop/gnome/url-handlers/https/command = 
b''/desktop/gnome/url-handlers/https/enabled = 
b''/desktop/gnome/url-handlers/http/command = 
b''/desktop/gnome/url-handlers/http/enabled = 
b''/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = b''/desktop/gnome/interface/gtk_theme 
= b''
modified.conffile..etc.default.chromium.browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: apport-crash i386 utopic

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1356210

Title:
  chromium-browser often crashes on page open, including
  chrome://settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1356210/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1301123] [NEW] chromium-browser crashed with SIGSEGV in content::ResourceDispatcher::OnReceivedRedirect()

[Eliah Kagan]

Public bug reported:

On a Saucy i386 system, Apport informed me Chromium had crashed. Flash
had crashed recently, so this may be a common Flash crash. But I'm not
sure yet, so I'm submitting this bug report. Unfortunately I don't have
much information beyond what's provided in the Apport-attached files.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: chromium-browser 33.0.1750.152-0ubuntu0.13.10.1~pkg984.1
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic i686
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: i386
Date: Tue Apr  1 23:02:46 2014
Desktop-Session:
 DESKTOP_SESSION = Lubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/Lubuntu:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2012-08-21 (588 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: chromium-browser\ --type=plugin\ 
--plugin-path=/usr/lib/adobe-flashplugin/libflashplayer.so\ --lang=en-US\ 
--channel=20818.14.7029800
SegvAnalysis:
 Segfault happened at: 0xb2d8ff2d:  mov0x14(%eax),%edx
 PC (0xb2d8ff2d) ok
 source 0x14(%eax) (0x0014) not located in a known VMA region (needed 
readable region)!
 destination %edx ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 ?? () from /usr/lib/chromium-browser/libs/libcontent.so
 content::ResourceDispatcher::OnReceivedRedirect(int, GURL const, 
content::ResourceResponseHead const) () from 
/usr/lib/chromium-browser/libs/libcontent.so
 content::ResourceDispatcher::DispatchMessage(IPC::Message const) () from 
/usr/lib/chromium-browser/libs/libcontent.so
 content::ResourceDispatcher::DispatchMessage(IPC::Message const) () from 
/usr/lib/chromium-browser/libs/libcontent.so
 ?? ()
Title: chromium-browser crashed with SIGSEGV in 
content::ResourceDispatcher::OnReceivedRedirect()
UpgradeStatus: Upgraded to saucy on 2013-11-13 (139 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'
modified.conffile..etc.default.chromium.browser: [deleted]

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301123

Title:
  chromium-browser crashed with SIGSEGV in
  content::ResourceDispatcher::OnReceivedRedirect()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1301123/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1298210] Re: Yelp does not show man pages

[Eliah Kagan]

Any of us may close the report by changing its status from New to
Invalid. But I think there may be value to this report: as I mentioned
on AU (http://askubuntu.com/questions/439801/man-command-does-not-work-
with-yelp?noredirect=1#comment574556_439839), I'm not sure why the
legacy behavior cannot also be supported. That would make this a
feature  request though (but if it's accepted, the triager can take that
into account in assigning severity).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1298210

Title:
  Yelp does not show man pages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1298210/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1272058] [NEW] chromium-browser crashed with SIGSEGV in magazine_chain_pop_head()

[Eliah Kagan]

Public bug reported:

chromium-browser 31.0.1650.63-0ubuntu0.13.10.1~20131204.1 crashed on
Lubuntu Saucy i386 while running in the background. I was not
interacting directly with Chromium at or within several minutes of the
time of the crash. This might be bug 926143.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: chromium-browser 31.0.1650.63-0ubuntu0.13.10.1~20131204.1
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: Wed Jan 22 13:15:55 2014
Desktop-Session:
 DESKTOP_SESSION = Lubuntu
 XDG_CONFIG_DIRS = /etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg
 XDG_DATA_DIRS = /usr/share/Lubuntu:/usr/local/share/:/usr/share/
Env:
 MOZ_PLUGIN_PATH = None
 LD_LIBRARY_PATH = None
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2012-08-21 (519 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: chromium-browser
SegvAnalysis:
 Segfault happened at: 0xb0930b2e g_slice_alloc+158:  mov(%edi),%edx
 PC (0xb0930b2e) ok
 source (%edi) (0xd23786b0) not located in a known VMA region (needed 
readable region)!
 destination %edx ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: chromium-browser
StacktraceTop:
 magazine_chain_pop_head (magazine_chunks=0xb84086d8) at 
/build/buildd/glib2.0-2.38.1/./glib/gslice.c:545
 thread_memory_magazine1_alloc (tmem=optimized out, ix=1) at 
/build/buildd/glib2.0-2.38.1/./glib/gslice.c:848
 g_slice_alloc (mem_size=mem_size@entry=12) at 
/build/buildd/glib2.0-2.38.1/./glib/gslice.c:1007
 g_list_copy_deep (list=0xb9fe2220, list@entry=0xba3d5e80, func=func@entry=0x0, 
user_data=user_data@entry=0x0) at 
/build/buildd/glib2.0-2.38.1/./glib/glist.c:636
 g_list_copy (list=0xba3d5e80) at 
/build/buildd/glib2.0-2.38.1/./glib/glist.c:585
Title: chromium-browser crashed with SIGSEGV in magazine_chain_pop_head()
UpgradeStatus: Upgraded to saucy on 2013-11-13 (70 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
chromium-default: CHROMIUM_FLAGS=
gconf-keys: /desktop/gnome/applications/browser/exec = 
b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = 
b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = 
b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser 
%s\n'/desktop/gnome/url-handlers/http/enabled = 
b'true\n'/desktop/gnome/session/required_components/windowmanager = 
b''/apps/metacity/general/compositing_manager = 
b''/desktop/gnome/interface/icon_theme = 
b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n'

** Affects: chromium-browser (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1272058

Title:
  chromium-browser crashed with SIGSEGV in magazine_chain_pop_head()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1272058/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1271497] [NEW] transmission-gtk crashed with SIGSEGV in tr_torrentInfo()

[Eliah Kagan]

*** This bug is a duplicate of bug 1222782 ***
https://bugs.launchpad.net/bugs/1222782

Public bug reported:

Transmission crashed on a Lubuntu Saucy i386 system (transmission
/transmission-gtk 2.82-0ubuntu1). I am unsure of the circumstances
surrounding the crash. I was seeding a number of torrents and
downloading none. The volume to which torrents were set to be downloaded
was full, and I had previously started a torrent and then removed it
after it couldn't run due to insufficient space. The crash occurred
*after* this, and I don't know if it really had anything to do with it.

Since being restarted, Transmission has continued working properly and
has not subsequently crashed.

I don't think I've ever had this particular crash before, even though
these circumstances have occurred before in Transmission on this system.
I suspect the free space issue is *not* relevant to the crash; I'm only
mentioning it in case my guess is mistaken.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: transmission-gtk 2.82-0ubuntu1
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: Tue Jan 21 14:55:29 2014
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2012-08-21 (518 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: transmission-gtk
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb7780a6a tr_torrentInfo+10:  cmpl   
$0x1753d,0x88(%edx)
 PC (0xb7780a6a) ok
 source $0x1753d ok
 destination 0x88(%edx) (0x0087) not located in a known VMA region 
(needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_torrentInfo ()
 tr_cpMissingBlocksInPiece ()
 ?? ()
 ?? ()
 tr_cacheFlushDone ()
Title: transmission-gtk crashed with SIGSEGV in tr_torrentInfo()
UpgradeStatus: Upgraded to saucy on 2013-11-13 (69 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: transmission (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271497

Title:
  transmission-gtk crashed with SIGSEGV in tr_torrentInfo()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1271497/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1153661] Re: The disk drive for /dev/mapper/cryptswap1 is not ready yet or not present

[Eliah Kagan]

For affected people looking for a workaround--this procedure might work,
as it is for the same or a very similar problem:

http://punygeek.blogspot.com/2012/10/ubuntu-1204-how-to-solve-disk-drive-for.html
http://askubuntu.com/a/342002/22949

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1153661

Title:
  The disk drive for /dev/mapper/cryptswap1 is not ready yet or not
  present

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1153661/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1204037] [NEW] abiword crashed with SIGABRT in FV_UnixSelectionHandles::FV_UnixSelectionHandles()

[Eliah Kagan]

Public bug reported:

AbiWord crashed on a Saucy amd64 system. I'm not sure of the
circumstances, because the error-reporting dialog did not trigger as
normal; my guess is that the crash was while AbiWord was launching or
quitting. So I don't know what triggered this crash.

This somewhat resembles bug 921756. Comparison of symbolic stack
(re)traces should make it possible to know if they're the same bug.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: abiword 3.0.0~svn20130523-1ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Fri Jul 19 02:38:51 2013
ExecutablePath: /usr/bin/abiword
InstallationDate: Installed on 2013-07-17 (5 days ago)
InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: abiword 
file:///home/username/Desktop/Matlab%20Production%20Server%20-%20Product%20Configuration%20Notes.odt
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: abiword
StacktraceTop:
 FV_UnixSelectionHandles::FV_UnixSelectionHandles (this=0x301bfe8, 
view=0x301b800, selection=...) at fv_UnixSelectionHandles.cpp:52
 FV_View::FV_View (this=0x301b800, pApp=0x14476b0, pParentData=optimized out, 
pLayout=0x2fcb400) at fv_View.cpp:304
 FV_View::copyTextToClipboard (this=optimized out, sIncoming=...) at 
fv_View.cpp:1067
 FV_View::cmdHyperlinkCopyLocation (this=this@entry=0x276d560, pos=optimized 
out) at fv_View_cmd.cpp:4075
 ap_EditMethods::hyperlinkCopyLocation (pAV_View=0x276d560) at 
ap_EditMethods.cpp:14307
Title: abiword crashed with SIGABRT in 
FV_UnixSelectionHandles::FV_UnixSelectionHandles()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: abiword (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204037

Title:
  abiword crashed with SIGABRT in
  FV_UnixSelectionHandles::FV_UnixSelectionHandles()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abiword/+bug/1204037/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1204175] [NEW] Xorg crashed with SIGABRT in __GI_raise()

[Eliah Kagan]

Public bug reported:

Xorg crashed on Saucy amd64. Unfortunately I am unsure of the
circumstances surrounding this crash; if it were not for Apport, I would
probably not be aware of it. This suggests the crash may have occurred
during at login or logout.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xserver-xorg-core 2:1.14.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Wed Jul 17 13:45:53 2013
ExecutablePath: /usr/bin/Xorg
InstallationDate: Installed on 2013-07-17 (6 days ago)
InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp 
vt7 -novtswitch -background none
ProcEnviron:
 
Signal: 6
SourcePackage: xorg-server
Stacktrace:
 #0  0x7f95e251f037 in __GI_raise (sig=6, sig@entry=error reading 
variable: Cannot access memory at address 0x7fff8e312978) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
 resultvar = 0
 pid = 1239
 selftid = 1239
 Cannot access memory at address 0x7fff8e312978
StacktraceTop: __GI_raise (sig=6, sig@entry=error reading variable: Cannot 
access memory at address 0x7fff8e312978) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:56
Title: Xorg crashed with SIGABRT in __GI_raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: xorg-server (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1204175

Title:
  Xorg crashed with SIGABRT in __GI_raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1204175/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1203755] [NEW] file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Eliah Kagan]

Public bug reported:

In a Saucy amd64 system I opened a .tar.xz archive (which I'd previously
created myself on another system with tar cf ... followed by xz -9v
...) and double-clicked on the single folder it contained, to view its
contents in file-roller itself before performing any extractions. file-
roller crashed.

I believe this is bug 723841 but I am not 100% sure without looking at a
good symbolic trace, so I'm posting this just in case. I'll try to
compare the trace as soon as there's a good one, unless someone else (or
the Apport retracing service bot) does so first.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: file-roller 3.8.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1
Uname: Linux 3.10.0-4-generic x86_64
ApportVersion: 2.11-0ubuntu1
Architecture: amd64
Date: Sat Jul 20 22:21:49 2013
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2013-07-17 (5 days ago)
InstallationMedia: Lubuntu 13.10 Saucy Salamander - Alpha amd64 (20130716)
MarkForUpload: True
ProcCmdline: file-roller 
file:///home/username/Downloads/Maplesoft.Maple.v13.0.LINUX.x64-TBE.tar.xz
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x41cb30:mov(%rbx),%rsi
 PC (0x0041cb30) ok
 source (%rbx) (0x0048) not located in a known VMA region (needed 
readable region)!
 destination %rsi ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: file-roller
StacktraceTop:
 ?? ()
 _gtk_marshal_BOOLEAN__BOXED (closure=0x2998cb0, return_value=0x7fff97fb62e0, 
n_param_values=optimized out, param_values=0x7fff97fb6390, 
invocation_hint=optimized out, marshal_data=optimized out) at 
/build/buildd/gtk+3.0-3.8.2/./gtk/gtkmarshalers.c:85
 g_closure_invoke (closure=0x2998cb0, return_value=0x7fff97fb62e0, 
n_param_values=2, param_values=0x7fff97fb6390, invocation_hint=0x7fff97fb6330) 
at /build/buildd/glib2.0-2.37.3/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x265a990, detail=detail@entry=0, 
instance=instance@entry=0x27be610, 
emission_return=emission_return@entry=0x7fff97fb6460, 
instance_and_params=instance_and_params@entry=0x7fff97fb6390) at 
/build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3582
 g_signal_emit_valist (instance=optimized out, signal_id=optimized out, 
detail=optimized out, var_args=var_args@entry=0x7fff97fb6528) at 
/build/buildd/glib2.0-2.37.3/./gobject/gsignal.c:3336
Title: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: file-roller (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace saucy

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203755

Title:
  file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1203755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1202847] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Eliah Kagan]

*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841

Comparison of symbolic stack traces indicates this is bug 723841. Other
descriptive information supports this (see the description of that bug
and of various duplicates). As for the different title, there may be
some variation in the function where SIGSEGV occurs, but this appears to
arise from (in)consistency between different symbolic stack traces (it
tends to change across a symbolic trace, in either direction).

Marking as duplicate; of course please comment if you think I might be
wrong (and feel free to un-dupe it if you're pretty sure I am).

** This bug has been marked a duplicate of bug 723841
   file-roller crashed with SIGSEGV in 
egg_tree_multi_drag_button_release_event()

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1202847

Title:
  file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1202847/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1203755] Re: file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Eliah Kagan]

*** This bug is a duplicate of bug 723841 ***
https://bugs.launchpad.net/bugs/723841

Comparison of the stack trace here to
https://bugs.launchpad.net/ubuntu/+source/file-
roller/+bug/723841/comments/3, in combination with the similarity in
circumstances triggering the crash, is sufficient to convince me this is
the same bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203755

Title:
  file-roller crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1203755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 875543] Re: can't eject cd rom : Inappropriate ioctl for device

[Eliah Kagan]

** Tags removed: 12.04
** Tags added: quantal raring

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875543

Title:
  can't eject cd rom : Inappropriate ioctl for device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1199448] [NEW] pcmanfm crashed with SIGSEGV in fm_file_info_is_dir()

[Eliah Kagan]

Public bug reported:

pcmanfm crashed on a Lubuntu Quantal i386 system, in a Lubuntu desktop
session. I don't believe I was actively using it at the time. My guess
is that the crash was on session logout, but I am not sure of that. I
don't know what triggered the crash or how to reproduce it. This
somewhat resembles expired bug 780385, but I'm not sure if they're
related.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: pcmanfm 1.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14
Uname: Linux 3.5.0-36-generic i686
ApportVersion: 2.6.1-0ubuntu12
Architecture: i386
Config_pcmanfm_System_Lubuntu: Error: [Errno 2] No such file or directory: 
'/etc/xdg/pcmanfm/lubuntu.conf'
Date: Sat Jul  6 18:08:38 2013
ExecutablePath: /usr/bin/pcmanfm
InstallationDate: Installed on 2012-08-21 (322 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
Pref_Config_System_Lubuntu:
 [Preferred Applications]
 WebBrowser=firefox.desktop
 MailClient=
ProcCmdline: pcmanfm --desktop --profile lubuntu
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb71870e9 fm_file_info_is_dir+25: mov
0x4(%edx),%eax
 PC (0xb71870e9) ok
 source 0x4(%edx) (0x0004) not located in a known VMA region (needed 
readable region)!
 destination %eax ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pcmanfm
StacktraceTop:
 fm_file_info_is_dir (fi=fi@entry=0x0) at base/fm-file-info.c:737
 on_folder_view_clicked (win=0x84ca0d8, fi=0x0, type=FM_FV_MIDDLE_CLICK, 
fv=0xb500bf00) at main-win.c:1278
 on_folder_view_clicked (fv=fv@entry=0xb500bf00, type=FM_FV_MIDDLE_CLICK, 
fi=0x0, win=0x84ca0d8) at main-win.c:1208
 g_cclosure_marshal_VOID__UINT_POINTER (closure=0x855f770, return_value=0x0, 
n_param_values=3, param_values=0xbf85c190, invocation_hint=0xbf85c13c, 
marshal_data=0x0) at /build/buildd/glib2.0-2.34.1/./gobject/gmarshal.c:1429
 g_closure_invoke (closure=0x855f770, return_value=return_value@entry=0x0, 
n_param_values=3, param_values=param_values@entry=0xbf85c190, 
invocation_hint=invocation_hint@entry=0xbf85c13c) at 
/build/buildd/glib2.0-2.34.1/./gobject/gclosure.c:777
Title: pcmanfm crashed with SIGSEGV in fm_file_info_is_dir()
UpgradeStatus: Upgraded to quantal on 2013-03-21 (110 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: pcmanfm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace quantal

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1199448

Title:
  pcmanfm crashed with SIGSEGV in fm_file_info_is_dir()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1199448/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157900] Re: add-apt-repository crashed with ImportError in get_ppa_info_from_lp(): No module named 'pycurl'

[Eliah Kagan]

This crash often happens to me when I terminate a running instance of
add-apt-repository with Ctrl+C (though not every time, see duplicate bug
1186492 for details). I've been able to make that happen on multiple
systems running different Ubuntu releases multiple times, so that might
be a way for people who cannot reproduce the bug to do so.

Dmitry Shachnev's analysis (https://bugs.launchpad.net/ubuntu/+source
/software-properties/+bug/1157900/comments/7) clarifies why Ctrl+C is
one way to produce the crash (get_ppa_info_from_lp() wrongly catches all
exceptions including KeyboardInterrupt). Thanks for the explanation!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157900

Title:
  add-apt-repository crashed with ImportError in get_ppa_info_from_lp():
  No module named 'pycurl'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1157900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1192594] [NEW] transmission-gtk crashed with SIGSEGV in g_type_check_instance_cast()

[Eliah Kagan]

Public bug reported:

On a Lubuntu i386 system running Transmission with the GTK+ frontend,
transmission crashed while seeding some torrents. There did not appear
to be any user interaction that triggered this crash.

This somewhat resembles bug 453428. To a lesser extent this resembles
bug 630679 (which has a different description of potentially triggering
events) and also bug bug 638166 and bug 638166 (where the name of the
function in which the segfault occurred was different, but it seems
likely that one of the two calls is nested inside the other and that the
different names arise from different incomplete symbolic stack traces).
To an even lesser extent (because of a combination of different
descriptions and different function names) this resembles bug 192515 and
bug 556822.

I am reporting a new bug, primarily because all those bugs currently
have status invalid (most of them have that status because no good
symbolic stack trace was ever obtained--which would make it difficult to
confirm that this is the same bug--or because they were not
reproducible).

After restarting Transmission, it appears to work normally, and it has
not yet crashed again (even seeding all the same torrents for hours).

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: transmission-gtk 2.61-0ubuntu2.2
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: Mon Jun 17 15:18:59 2013
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2012-08-21 (300 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: transmission-gtk
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb6f45598 g_type_check_instance_cast+56:  mov
(%eax),%ebp
 PC (0xb6f45598) ok
 source (%eax) (0x) not located in a known VMA region (needed 
readable region)!
 destination %ebp ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 g_type_check_instance_cast (type_instance=0xb7e22000, iface_type=3083338184) 
at /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:3997
 ?? ()
 gdk_threads_dispatch (data=data@entry=0xb850fa20) at 
/build/buildd/gtk+3.0-3.6.0/./gdk/gdk.c:788
 g_idle_dispatch (source=source@entry=0xb8329510, callback=0xb7141e80 
gdk_threads_dispatch, user_data=0xb850fa20) at 
/build/buildd/glib2.0-2.34.1/./glib/gmain.c:4806
 g_main_dispatch (context=0xb7bb6ad8) at 
/build/buildd/glib2.0-2.34.1/./glib/gmain.c:2715
Title: transmission-gtk crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: Upgraded to quantal on 2013-03-21 (88 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: transmission (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace quantal

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192594

Title:
  transmission-gtk crashed with SIGSEGV in g_type_check_instance_cast()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1192594/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1186492] [NEW] add-apt-repository sometimes crashes when SIGINT (Ctrl+C) is sent: crashed with ImportError in get_ppa_info_from_lp(): No module named 'pycurl'

[Eliah Kagan]

Public bug reported:

It appears add-apt-repository will sometimes crash instead of properly
terminating, when SIGINT is sent (e.g., by Ctrl_C being pressed).

This crash happened when I entered a sudo add-apt-repository ...
command with a typo in the name of the PPA I was adding. This crash was
probably not triggered even partially by special syntax--the typo was
just a misspelling.

The expected behavior would be for add-apt-repository not to crash when
Ctrl+C is pressed (or when SIGINT is otherwise sent). Whether or not any
substantive cleanup is performed when Ctrl+C is pressed, it should be
considered a bug for an actual crash to occur in response to it. The
primary negative impact of this bug on users is probably that, on most
stable systems, Apport/Whoopsie runs when a crash occurs. But even if
the crash were silent, it is still a bug.

With that said, this is unlikely to be a serious bug. Its impact is
minimal, it does not ever prevent add-apt-repository from being used
effectively, and add-apt-repository does terminate when Ctrl+C is given
(it just crashes sometimes while doing so). Furthermore, add-apt-
repository probably only crashes some of the time--rather than every
time--that SIGINT is sent.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: software-properties-common 0.92.17
ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13
Uname: Linux 3.8.0-24-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.1
Architecture: amd64
Date: Sat Jun  1 02:12:39 2013
ExecutablePath: /usr/bin/add-apt-repository
InstallationDate: Installed on 2013-05-29 (2 days ago)
InstallationMedia: Lubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:gfire/fire
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:gfire/fire']
SourcePackage: software-properties
Title: add-apt-repository crashed with ImportError in get_ppa_info_from_lp(): 
No module named 'pycurl'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: software-properties (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-crash raring

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1186492

Title:
  add-apt-repository sometimes crashes when SIGINT (Ctrl+C) is sent:
  crashed with ImportError in get_ppa_info_from_lp(): No module named
  'pycurl'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1186492/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1180499] [NEW] audacious crashed with SIGSEGV

[Eliah Kagan]

Public bug reported:

On a Quantal i386 system, audacious crashed when quitting. It usually
does not crash; I cannot reproduce this deliberately.

Earlier versions of audacious on earlier Ubuntu releases, on this and
other machines, and on both i386 and amd64 systems, have crashed for me.
So perhaps the problem is triggered by some feature of my music library.
It is, and has been, very large -- perhaps larger than the music
libraries with which audacious has been tested. In particular, my main
playlist contains 54261 tracks.

All the previous crashes (each of which was with an older version of
audacious on an older Ubuntu release) on quitting appeared to be the
same bug. See bug 691378 (and its duplicates). I suspect this may be the
same bug as bug 691378. Since (1) the machine on which the crash
reported here occurred did not have many debug symbols installed, and
(2) this occurs much less frequently than it used to and I'm not sure I
can produce it again, I am reporting this. Hopefully Apport retracing
service can produce a stack trace with enough detail that it can be
compared to at least one of the stack traces posted in bug 691378.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: audacious 3.2.3-1
ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
Uname: Linux 3.5.0-27-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Wed May 15 13:57:25 2013
Disassembly: = 0xb329092f: Cannot access memory at address 0xb329092f
ExecutablePath: /usr/bin/audacious
InstallationDate: Installed on 2012-08-21 (267 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: audacious
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb329092f:  Cannot access memory at address 
0xb329092f
 PC (0xb329092f) not located in a known VMA region (needed executable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: audacious
Stacktrace:
 #0  0xb329092f in ?? ()
 No symbol table info available.
 #1  0xb1da6058 in ?? ()
 No symbol table info available.
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 ?? ()
Title: audacious crashed with SIGSEGV
UpgradeStatus: Upgraded to quantal on 2013-03-21 (55 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: audacious (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace quantal

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180499

Title:
  audacious crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1180499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1176354] [NEW] thunar crashed with SIGSEGV

[Eliah Kagan]

Public bug reported:

I ran thunar 1.6.2-0ubuntu1 remotely via ssh -X; the server (on which it
ran) was Raring i386. The desktop environment on the *client* (in case
this is an interface problem) is LXDE; the client is an Lubuntu Oneiric
i386 system. Notification area integration (for the tray icon
accompanying file copy dialogs) worked fine.

I was copying a number of files--in a single job, not multiple
simultaneous jobs--from an ext4 volume to an NTFS volume. During the
copy operation, I clicked on a volume on the list on the left. This was
in one open tab. Then I switched to another open tab. Either at that
point, or soon thereafter, Thunar segfaulted.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: thunar 1.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic i686
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
Date: Sat May  4 09:18:00 2013
Disassembly: = 0x0:Cannot access memory at address 0x0
ExecutablePath: /usr/bin/thunar
ExecutableTimestamp: 1356872238
InstallationDate: Installed on 2005-04-15 (2940 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120327.1)
MarkForUpload: True
ProcCmdline: thunar
ProcCwd: /home/ek
ProcEnviron:
 TERM=xterm
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=set
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: thunar
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: thunar crashed with SIGSEGV
UpgradeStatus: Upgraded to raring on 2013-03-20 (45 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo

** Affects: thunar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace raring

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176354

Title:
  thunar crashed with SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1176354/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1132030] Re: Facebook account setup opens in external browser, unusable

[Eliah Kagan]

As BlueCase says, this will likely occur again and again from time to
time as services have similar problems, and this is fixable in gnome-
cocntrol-center-signon. Probably the best thing to do would be for
someone who was able to reproduce this before it was fixed on Facebook's
side to file a new bug report explaining how this situation reflects a
bug in gnome-control-center-signon too. It should also be filed upstream
(and the upstream bug added to the new bug's Launchpad page), since this
is somewhat unlikely to be fixed in an Ubuntu or Debian specific patch
or even to be considered as qualifying for an SRU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132030

Title:
  Facebook account setup opens in external browser, unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1132030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1162928] [NEW] totem-video-thumbnailer crashed with SIGSEGV in oil_init()

[Eliah Kagan]

Public bug reported:

I was viewing a couple folders of video files in pcmanfm on a Lubuntu
11.10 i386 system. One folder was of .mkv files; the other was of .avi
files. Nothing seemed to go wrong--pcmanfm did not itself crash, and all
the files were properly thumbnailed. I was not using Totem itself to
open any of the files, but I was playing some with VLC.

Apport informed me that totem had crashed, and when I saw the crash was
in the binary totem-video-thumbnailer, I assumed it happened because of
some problem thumbnailing the videos in pcmanfm.

This crash resembles these other two bugs:

https://bugs.launchpad.net/ubuntu/+source/liboil/+bug/403110
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/980651

But I cannot yet tell if it is really the same as either. It's also a
little similar to these bugs:

https://bugs.launchpad.net/ubuntu/+source/totem/+bug/184536
https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10-ffmpeg/+bug/420930

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: totem 3.4.3-0ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-39.62-generic 3.2.39
Uname: Linux 3.2.0-39-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Sun Mar 31 21:57:34 2013
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2012-08-21 (222 days ago)
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
MarkForUpload: True
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 128 
file:///media/username/Noether/TV/Freaks%20and%20Geeks/freaks.and.geeks.s01e08-vrs.avi
 /home/username/.thumbnails/normal/10a9af21a855a1ab87b2c5ede83465c2.png
ProcEnviron:
 PATH=(custom, user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x1d98ce28:  mov0x10(%eax),%edx
 PC (0x1d98ce28) ok
 source 0x10(%eax) (0x0010) not located in a known VMA region (needed 
readable region)!
 destination %edx ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: totem
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 oil_init () from /usr/lib/i386-linux-gnu/liboil-0.3.so.0
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so
 ?? () from /usr/lib/i386-linux-gnu/gstreamer-0.10/libgstflump3dec.so
Title: totem-video-thumbnailer crashed with SIGSEGV in oil_init()
UpgradeStatus: Upgraded to quantal on 2013-03-21 (11 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: totem (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace quantal

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162928

Title:
  totem-video-thumbnailer crashed with SIGSEGV in oil_init()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1162928/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157400] [NEW] unity-greeter crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

Public bug reported:

I logged into a Unity session on a Quantal i386 system with old hardware
--an Nvidia GeForce 5200 graphics card. The screen flickered yellowish,
then went to black. There was no visible interface. I restarted lightdm
to get back to the graphical login screen. Soon after, I found that
unity-greeter had crashed. I'm guessing that this is secondary to the
video incompatibility rather than the cause of it, but it is
specifically the crash in unity-greeter that I'm reporting here.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity-greeter 12.10.4-0ubuntu5.1
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Tue Mar 19 15:49:06 2013
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2005-04-15 (2894 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120327.1)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb73398a0:  mov(%edi),%eax
 PC (0xb73398a0) ok
 source (%edi) (0x) not located in a known VMA region (needed 
readable region)!
 destination %eax ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: unity-greeter crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to quantal on 2013-03-19 (0 days ago)
UserGroups:

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-crash i386 need-i386-retrace quantal

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157400

Title:
  unity-greeter crashed with SIGSEGV in g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1157400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1157400] Re: unity-greeter crashed with SIGSEGV in g_main_context_dispatch()

[Eliah Kagan]

** Description changed:

- I logged into a Unity session on a Quantal i386 system with old hardware
- --an Nvidia GeForce 5200 graphics card. The screen flickered yellowish,
- then went to black. There was no visible interface. I restarted lightdm
- to get back to the graphical login screen. Soon after, I found that
- unity-greeter had crashed. I'm guessing that this is secondary to the
- video incompatibility rather than the cause of it, but it is
- specifically the crash in unity-greeter that I'm reporting here.
+ On a Quantal i386 system, the LightDM login screen quit without warning
+ as I started entering my password. This happened a few times in a row,
+ but it had not happened the previous time I'd run lightdm, and it didn't
+ happen any subsequent times. (I'd recently stopped and restarted the
+ lightdm service, and I did that again to overcome the problem; then the
+ greeter worked and I was able to log in.)
+ 
+ I discovered soon afterwards that unity-greeter had crashed. I presume
+ this corresponds to one of the times lightdm quit as I started to enter
+ my password.
+ 
+ In case it's relevant, I'd previously logged into a Unity session. This
+ system has old hardware--an Nvidia GeForce 5200 graphics card. The
+ screen had flickered yellowish, then went to black. There was no visible
+ interface. I restarted lightdm to get back to the graphical login
+ screen. Please note that this is a description of the events that led me
+ to run sudo stop lightdm followed by sudo start lightdm the first
+ time, leading to a state where unity-greeter crashed. I'm not sure if
+ the problems I had with Unity itself are relevant, and I understand they
+ are probably not since unity-greeter is not really related to Unity
+ except in that it is themed similarly.
+ 
+ Please note that this bug report is for the unity-greeter crash and
+ *not* for the graphics issue.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: unity-greeter 12.10.4-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
  Uname: Linux 3.5.0-26-generic i686
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: i386
  Date: Tue Mar 19 15:49:06 2013
  ExecutablePath: /usr/sbin/unity-greeter
  InstallationDate: Installed on 2005-04-15 (2894 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 
(20120327.1)
  MarkForUpload: True
  ProcCmdline: /usr/sbin/unity-greeter
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/false
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/false
  SegvAnalysis:
-  Segfault happened at: 0xb73398a0:mov(%edi),%eax
-  PC (0xb73398a0) ok
-  source (%edi) (0x) not located in a known VMA region (needed 
readable region)!
-  destination %eax ok
+  Segfault happened at: 0xb73398a0:mov(%edi),%eax
+  PC (0xb73398a0) ok
+  source (%edi) (0x) not located in a known VMA region (needed 
readable region)!
+  destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-greeter
  StacktraceTop:
-  ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
-  ?? ()
-  ?? ()
-  ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
-  g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
+  ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
+  ?? ()
+  ?? ()
+  ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
+  g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
  Title: unity-greeter crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2013-03-19 (0 days ago)
  UserGroups:

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1157400

Title:
  unity-greeter crashed with SIGSEGV in g_main_context_dispatch()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1157400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1078993] Re: [System Product Name, ATI RS880 HDMI, audio (Radeon HD 4200) No sound at all

[Eliah Kagan]

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed = New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078993

Title:
  [System Product Name, ATI RS880 HDMI, audio (Radeon HD 4200)  No sound
  at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1078993/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1078993] Re: [System Product Name, ATI RS880 HDMI, audio (Radeon HD 4200) No sound at all

[Eliah Kagan]

Are you logged in as Guest? There are a lot of Permission denied
errors in the information sent by Apport, sometimes even when trying to
access information that's available even to limited users (but not
necessarily available to Guest). And the error from when Apport tried to
run fuser with pkexec (to report Symptom_DevicesInUse) is quite unusual,
but I am able to produce this exact error by attempting to run a
command-line program with pkexec from a Guest session.

If you were logged in as Guest when you reported this bug, is that
because sounds is only broken when you log in as Guest? Does sound work
when you log in as a real user? If the problem affects the Guest
account and other accounts equally, I recommend logging in with a normal
user account and running apport-collect 1078993 (without the quotes)
to add information to this bug. Alternatively, you could re-report the
bug while logged in as a normal user, then make this bug a duplicate of
the new one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078993

Title:
  [System Product Name, ATI RS880 HDMI, audio (Radeon HD 4200)  No sound
  at all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1078993/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025553] Re: Plugin fails to load in Chrome

[Eliah Kagan]

I reproduced the bug on a Natty i386 virtual machine, then installed the
recently committed Natty binary packages (from https://launchpad.net
/~ubuntu-security-proposed/+archive/ppa/+build/3725259).

They fix the bug for me on Natty as well.

These were the working package versions (on the Natty VM):

icedtea-plugin/icedtea-6-plugin/icedtea-netx 1.2-2ubuntu0.11.04.3
icedtea6-plugin 6b21.2-2ubuntu0.11.04.3
chromium-browser 18.0.1025.168~r134367-0ubuntu0.11.04.1

(Also, you may notice that I only listed two of the four packages in my
last comment. But when I tested it I did also install the other two,
which are architecture-independent and built on
https://launchpad.net/builders/roseapple along with the i386 packages; I
just neglected to list their versions. These other two packages,
installed on my Oneiric amd64 machine, were icedtea-plugin
1.2-2ubuntu0.11.10.3 and icedtea6-plugin 6b21.2-2ubuntu0.11.10.3.)

** Tags added: verification-done-natty

** Tags removed: verification-needed
** Tags added: verification-done

** Tags removed: verification-done-natty verification-done-oneiric
verification-done-precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025553

Title:
  Plugin fails to load in Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1025553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1025553] Re: Plugin fails to load in Chrome

[Eliah Kagan]

The recently committed package fixes the bug for me on my Oneiric amd64
system.

icedtea-6-plugin/icedtea-netx 1.2-2ubuntu0.11.10.3
chromium-browser 18.0.1025.168~r134367-0ubuntu0.11.10.1
Tested with http://www.java.com/en/download/testjava.jsp.

I used the debs from https://launchpad.net/~ubuntu-security-
proposed/+archive/ppa/+build/3725266 since the binary packages aren't
available from oneiric-proposed yet (at least via the US mirror).

** Tags added: verification-done-oneiric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1025553

Title:
  Plugin fails to load in Chrome

To manage notifications about this bug go to:
https://bugs.launchpad.net/icedtea/+bug/1025553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 875543] Re: can't eject cd rom : Inappropriate ioctl for device

[Eliah Kagan]

** Tags added: 12.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875543

Title:
  can't eject cd rom : Inappropriate ioctl for device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/875543/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 761830] Re: grub2 still hands off to blank tty7 on non-Server command-line-only systems and some Server systems

[Eliah Kagan]

** Tags added: quantal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/761830

Title:
  grub2 still hands off to blank tty7 on non-Server command-line-only
  systems and some Server systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/761830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1029238] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/apt/history.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1029238/+attachment/3236448/+files/history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029238

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1029238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1029238] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/apt/term.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1029238/+attachment/3236450/+files/term.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029238

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1029238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1029238] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/dpkg.log
   https://bugs.launchpad.net/bugs/1029238/+attachment/3236434/+files/dpkg.log

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029238

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1029238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1024463] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

** Attachment added: dpkg.log
   https://bugs.launchpad.net/bugs/1024463/+attachment/3222407/+files/dpkg.log

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024463

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1024463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1024463] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

** Attachment added: /var/log/apt/term.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1024463/+attachment/3222421/+files/term.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024463

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1024463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1024463] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

** Attachment added: /var/log/apt/history.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1024463/+attachment/3222422/+files/history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1024463

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1024463/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1023717] Re: soundconverter crashed with Error in notification(): GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded: Exceeded maximum number of notifications

[Eliah Kagan]

** Attachment added: log file from creation of FLAC files (not by Sound 
Converter)
   
https://bugs.launchpad.net/bugs/1023717/+attachment/3220502/+files/Trent%20Reznor%20And%20Atticus%20Ross%20-%20The%20Girl%20With%20The%20Dragon%20Tattoo.log

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023717

Title:
  soundconverter crashed with Error in notification():
  GDBus.Error:org.freedesktop.Notifications.MaxNotificationsExceeded:
  Exceeded maximum number of notifications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/soundconverter/+bug/1023717/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 716597] Re: Invalid username indication not clear

[Eliah Kagan]

*** This bug is a duplicate of bug 549195 ***
https://bugs.launchpad.net/bugs/549195

** This bug has been marked a duplicate of bug 549195
   Ubiquity should give visual feedback that username cannot contains capital 
letter(s)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/716597

Title:
  Invalid username indication not clear

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/716597/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1019244] Re: pcmanfm crashed with SIGSEGV in free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019244

Title:
  pcmanfm crashed with SIGSEGV in free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1019244/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1017411] Re: clementine crashed with SIGABRT in qt_message_output()

[Eliah Kagan]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017411

Title:
  clementine crashed with SIGABRT in qt_message_output()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/1017411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1017411] [NEW] clementine crashed with SIGABRT in qt_message_output()

[Eliah Kagan]

Public bug reported:

I opened Clementine and it crashed. I recently switched from LXDE to
Xfce; I also recently had terminated Clementine with SIGKILL after it
became unresponsive when the drive containing my music library became
inaccessible (but this crash report is not from that Clementine
instance). Perhaps one or both of these developments explains why it
crashes now -- every time I try to run it -- but did not crash before
with the same settings and music library.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: clementine 1.0.1+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
ApportVersion: 2.0.1-0ubuntu10
Architecture: amd64
Date: Mon Jun 25 05:39:10 2012
ExecutablePath: /usr/bin/clementine
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413.1)
ProcCmdline: clementine
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: clementine
StacktraceTop:
 ?? ()
 qt_message_output(QtMsgType, char const*) () from 
/usr/lib/x86_64-linux-gnu/libQtCore.so.4
 ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
 Database::ExecCommands(QString const, QSqlDatabase, int) ()
Title: clementine crashed with SIGABRT in qt_message_output()
UpgradeStatus: Upgraded to precise on 2012-05-22 (33 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Affects: clementine (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1017411

Title:
  clementine crashed with SIGABRT in qt_message_output()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/1017411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1014277] Re: Ubuntu Software Center does not installing packages from Local repository

[Eliah Kagan]

In a Terminal window, please run this command, which will automatically
add important technical information to this bug report:

apport-collect 1014277

In the future, if you report bugs with Apport (for example, by running
ubuntu-bug with the package name or running process PID), this
information (and sometimes even more valuable information) will be
automatically included. See
https://help.ubuntu.com/community/ReportingBugs for more information on
bug reporting best practices.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014277

Title:
  Ubuntu Software Center does not installing packages from Local
  repository

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1014277/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 773368] Re: Could not open certain PNG images

[Eliah Kagan]

*** This bug is a duplicate of bug 172416 ***
https://bugs.launchpad.net/bugs/172416

@Kushal
This is happening because eog uncritically assumes filetype from filename. Most 
other modern image viewers look inside the image file to figure out what kind 
of image it is, which is why they do not have this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773368

Title:
  Could not open certain PNG images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 773368] Re: Could not open certain PNG images

[Eliah Kagan]

*** This bug is a duplicate of bug 172416 ***
https://bugs.launchpad.net/bugs/172416

@Kushal
It is no longer necessary for you to attach any files or provide anymore 
information--there is already a bug for this (bug 172416), and I'm setting this 
as a duplicate of it.

** This bug has been marked a duplicate of bug 172416
   eog determines image type from filename

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773368

Title:
  Could not open certain PNG images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1011114] Re: openbox crashed with SIGABRT in client_configure()

[Eliah Kagan]

*** This bug is a duplicate of bug 938379 ***
https://bugs.launchpad.net/bugs/938379


** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104

Title:
  openbox crashed with SIGABRT in client_configure()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1011114] Re: openbox crashed with SIGABRT in client_configure()

[Eliah Kagan]

*** This bug is a duplicate of bug 938379 ***
https://bugs.launchpad.net/bugs/938379


** Attachment added: /home/ek/.config/openbox/lubuntu-rc.xml
   
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/104/+attachment/3183167/+files/lubuntu-rc.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/104

Title:
  openbox crashed with SIGABRT in client_configure()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1011399] Re: openbox crashed with SIGABRT in client_configure()

[Eliah Kagan]

*** This bug is a duplicate of bug 938379 ***
https://bugs.launchpad.net/bugs/938379


** Description changed:

  I think this is bug 938379, but it definitely did not happen while I
  closed a context menu. I had highlighted text in an LXTerminal, and I
- clicked in AbiWord, and this crash happened.
+ clicked in Gedit, and this crash happened.
  
  Hopefully the Apport retracing service bot will determine if this is the
  same crash as bug 938379.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: openbox 3.5.0-2ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu9
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Jun 11 00:40:24 2012
  ExecutablePath: /usr/bin/openbox
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110413.1)
  ProcCmdline: openbox --config-file 
/home/username/.config/openbox/lubuntu-rc.xml
  ProcEnviron:
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  Signal: 6
  SourcePackage: openbox
  StacktraceTop:
-  client_configure ()
-  moveresize_end ()
-  ?? ()
-  ?? () from /usr/lib/libobt.so.0
-  g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
+  client_configure ()
+  moveresize_end ()
+  ?? ()
+  ?? () from /usr/lib/libobt.so.0
+  g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: openbox crashed with SIGABRT in client_configure()
  UpgradeStatus: Upgraded to precise on 2012-05-22 (19 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011399

Title:
  openbox crashed with SIGABRT in client_configure()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openbox/+bug/1011399/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 773368] Re: Could not open certain PNG images

[Eliah Kagan]

The original reporter (Kushal) indicates that this bug still occurs with
Precise, so I am changing this back from Expired to New.

@Kushal
Can you attach a few .png images (or at least one) that cause this problem on 
your system, and a few .png images (or at least one) that do not? Such 
attachments may make it a lot easier to figure out what is going wrong. Please 
also add technical information to this bug about your current system by opening 
a Terminal window (Ctrl+Alt+T) and running: apport-collect 773368

** Changed in: eog (Ubuntu)
   Status: Expired = New

** Tags added: precise

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/773368

Title:
  Could not open certain PNG images

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/773368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1009915] Re: reporting some bugs apparently does nothing

[Eliah Kagan]

** Also affects: apport
   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/1009915

Title:
  reporting some bugs apparently does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1009915/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1009915] Re: reporting some bugs apparently does nothing

[Eliah Kagan]

I'm also having this bug, on a Lubuntu Precise amd64 system with apport
2.0.1-0ubuntu9 and apport-gtk 2.0.1-0ubuntu9. It started when I upgraded
from Oneiric to Precise. In contrast, Apport crash reporting works
correctly on another machine that has Ubuntu (not Lubuntu) Precise i386
(installed from scratch).

This also happens when I try to submit a report for a .crash file in
/var/crash with ubuntu-bug or apport-cli.

ek@Apok:/var/crash$ apport-cli _usr_bin_audacious.1000.crash 

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (60.1 MB)
  E: Examine locally
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/E/V/K/I/C): s
ek@Apok:/var/crash$

xdg-open and sensible-browser both work and behave correctly when issued
from the command-line. I don't know if the problem is in submitting the
crash data or opening the browser, but I strongly suspect that it's in
submitting the crash data, because I am never told that crash data is
submitted.

This problem is not due to the bugs being reported being identified as
duplicates. I have verified this by simulating a segmentation fault in
nano by sending it SIGSEGV with kill. The apport service is triggered
and collects the data, but I am never told it is being sent or given a
web browser tab/window in which to report the bug.

I've tried rebooting and manually stopping and restarting the apport
service (though I don't think this is the problem with the service
itself, which seems to create .crash files just fine).

I have a number of crash bugs in Lubuntu Precise that would be
considerably harder for me to report because of this. I am also
considering early-adopting Lubuntu Quantal Alpha 1 on one of my
machines, but I am concerned that if I did, my efforts might be
considerably less useful to the community if my ability to report
crashes is hindered.

If anyone is running Lubuntu Precise or Quantal and does *not* have this
problem, I think it would be valuable to post about that here.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009915

Title:
  reporting some bugs apparently does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1009915/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1009915] Re: reporting some bugs apparently does nothing

[Eliah Kagan]

*** This bug is a duplicate of bug 994921 ***
https://bugs.launchpad.net/bugs/994921

** This bug has been marked a duplicate of bug 994921
   'ubuntu-bug /var/crash/app.crash' should still allow manual bug filing

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009915

Title:
  reporting some bugs apparently does nothing

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1009915/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1009697] Re: Wubi download is in a loop

[Eliah Kagan]

I've just tested this, and the Start download link at
http://www.ubuntu.com/download/desktop/windows-installer is working fine
for me. It brings me to http://www.ubuntu.com/download/desktop/thank-
you?distro=wubirelease=bits= where a download for wubi.exe starts
automatically.

This works correctly for me (i.e., I am unable to reproduce this bug) in:
- Firefox 13.0 [firefox 13.0+build1-0ubuntu0.12.04.1], on Ubuntu Precise
- Chromium 18.0.1025.168 (Developer Build 134367 Linux) [chromium-browser 
18.0.1025.168~r134367-0ubuntu0.12.04.1], on Ubuntu Precise
- Google Chrome 19.0.1084.52 m, on Windows 7

If you had this bug before, do you still have it now? If not, perhaps
it's just been fixed, or perhaps the problem is just with mirrors
serving bad links, as Nicholas Skaggs has suggested.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009697

Title:
  Wubi download is in a loop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-website/+bug/1009697/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 995522] Re: pcmanfm assert failure: *** glibc detected *** pcmanfm: malloc(): smallbin double linked list corrupted: 0x0000000001702630 ***

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/995522

Title:
  pcmanfm assert failure: *** glibc detected *** pcmanfm: malloc():
  smallbin double linked list corrupted: 0x01702630 ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/995522/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985998] Re: pcmanfm crashed with SIGSEGV in malloc_consolidate()

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985998

Title:
  pcmanfm crashed with SIGSEGV in malloc_consolidate()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/985998/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 861363] Re: pcmanfm assert failure: *** glibc detected *** pcmanfm: corrupted double-linked list: 0x08917160 ***

[Eliah Kagan]

I have just reported bug 985998, which I think is probably a duplicate
of this bug, but I am not sure.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861363

Title:
  pcmanfm assert failure: *** glibc detected *** pcmanfm: corrupted
  double-linked list: 0x08917160 ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/861363/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 985356] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/985356

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/985356/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 902617] Re: pcmanfm assert failure: *** glibc detected *** pcmanfm: double free or corruption (out): 0x08c65b20 ***

[Eliah Kagan]

Reproduced on a Lubuntu Oneiric amd64 system.

** Tags added: amd64

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/902617

Title:
  pcmanfm assert failure: *** glibc detected *** pcmanfm: double free or
  corruption (out): 0x08c65b20 ***

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/902617/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 983499] Re: unity-2d-shell crashed with SIGSEGV in QDBusAbstractInterface::asyncCallWithArgumentList()

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/983499

Title:
  unity-2d-shell crashed with SIGSEGV in
  QDBusAbstractInterface::asyncCallWithArgumentList()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/983499/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 826316] Re: pcmanfm crashed with SIGSEGV in magazine_chain_pop_head()

[Eliah Kagan]

As indicated in the original bug report, the system on which the bug
occurred was Natty, which *is* a currently supported version of Ubuntu.

Since I have no idea what triggered the problem, and it has not happened
since, even when copying files of similar size and under similar
circumstances, it seems unlikely that I will be able to reproduce it in
the near future on any Ubuntu system. As no one else has reported
experiencing it, I'm marking this Invalid.

If I experience this again, it would probably be on a new Ubuntu release
--either Oneiric or Precise. If that happens, I'll file a new report
with attached information including a stack trace, and if I'm confident
it's the same issue as this, then I'll mark this a duplicate of the new
report.

** Changed in: pcmanfm (Ubuntu)
   Status: Incomplete = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/826316

Title:
  pcmanfm crashed with SIGSEGV in magazine_chain_pop_head()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/826316/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 698197] Re: pcmanfm crashed with SIGSEGV in on_auto_scroll()

[Eliah Kagan]

I reported this bug after it happening on a Maverick system (as detailed
in the original bug report). Maverick is still supported, through the
end of this month. So I'm unsure what you mean when you ask if I can
reproduce this on a supported release.

In any case, I probably cannot reproduce it at all, on any release,
because I have no good idea what triggered. However, 2 other users have
indicated it affects them, so perhaps they will be able to provide more
information.

I'm tempted to change this from Invalid to Confirmed (and request that
Charlie Kravetz mark it back to Triaged), since the message describing
why it was changed to Invalid gives a rationale that is factually
incorrect. But I will instead wait, with the hope that your reasoning is
good, and just poorly expressed. (Did you use the wrong message template
when marking the bug incomplete?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/698197

Title:
  pcmanfm crashed with SIGSEGV in on_auto_scroll()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/698197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 961307] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/961307

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/961307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 958703] Re: bamfdaemon crashed with SIGABRT in raise()

[Eliah Kagan]

** Visibility changed to: Public

** Description changed:

- On a Precise Beta 1 i386 live CD system with bamfdaemon
- 0.2.110-0ubuntu1, I right-clicked a folder in Nautilus and clicked
- Sharing Options. I checked the box to shared the folder and, when
- prompted, told it to go ahead and install the necessary packages. But I
- had forgotten to connect to my wireless network, so the installation
- failed. I tried to go to the original window and click cancel, but was
- informed of this crash. I am unsure of which interface interation
- prompted the crash. I'm sorry I don't have a more precise description of
- what occurred.
+ On a Precise Beta 1 i386 live DVD desktop system running Unity 2D with
+ bamfdaemon 0.2.110-0ubuntu1 and unity-2d 5.4.0-0ubuntu1, I right-clicked
+ a folder in Nautilus and clicked Sharing Options. I checked the box to
+ shared the folder and, when prompted, told it to go ahead and install
+ the necessary packages. But I had forgotten to connect to my wireless
+ network, so the installation failed. I tried to go to the original
+ window and click cancel, but was informed of this crash. I am unsure of
+ which interface interation prompted the crash. I'm sorry I don't have a
+ more precise description of what occurred.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: bamfdaemon 0.2.110-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.93-0ubuntu2
  Architecture: i386
  CasperVersion: 1.305
  Date: Tue Mar 22 13:07:07 2005
  ExecutablePath: /usr/lib/bamf/bamfdaemon
  LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301)
  ProcCmdline: /usr/lib/bamf/bamfdaemon
  ProcEnviron:
-  SHELL=/bin/bash
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
  Signal: 6
  SourcePackage: bamf
  StacktraceTop:
-  raise () from /lib/i386-linux-gnu/libc.so.6
-  abort () from /lib/i386-linux-gnu/libc.so.6
-  g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
-  g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
-  ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
+  raise () from /lib/i386-linux-gnu/libc.so.6
+  abort () from /lib/i386-linux-gnu/libc.so.6
+  g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
+  g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
+  ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
  Title: bamfdaemon crashed with SIGABRT in raise()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm lpadmin sambashare sudo

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/958703

Title:
  bamfdaemon crashed with SIGABRT in raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/958703/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 958716] Re: ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled()

[Eliah Kagan]

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/958716

Title:
  ubuntu-sso-login crashed with SIGSEGV in QSocketNotifier::setEnabled()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/958716/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 459851] Re: can't use CTRL + C for copy'n'paste

[Eliah Kagan]

Fixed x64 tag to amd64 (the correct architecture name for any 64-bit
x86-compatible PC or Mac) and added names of all the Ubuntu releases in
the duplicates.

** Tags removed: x64
** Tags added: amd64 lucid maverick natty oneiric

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/459851

Title:
  can't use CTRL + C for copy'n'paste

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/459851/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 827934] Re: colord crashed with SIGABRT in raise()

[Eliah Kagan]

@Helge Jung
When I got this crash, I wasn't explicitly configuring a printer either. But it 
went away when I booted the live CD (and entered a desktop session) with the 
printer disconnected 
(https://bugs.launchpad.net/ubuntu/+source/colord/+bug/827934/comments/12). If 
you disconnect all your printers (and scanners), does that make the problem go 
away? Also, is this happening to you on an installed system or on a live CD?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/827934

Title:
  colord crashed with SIGABRT in raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/colord/+bug/827934/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 936731] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: AptTerminalLog.txt
   
https://bugs.launchpad.net/bugs/936731/+attachment/2760754/+files/AptTerminalLog.txt

** Visibility changed to: Public

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936731

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 936731] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/apt/term.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+attachment/2760768/+files/term.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936731

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 936731] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/apt/history.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+attachment/2760770/+files/history.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936731

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 936731] Re: pcmanfm crashed with SIGSEGV in __GI___libc_free()

[Eliah Kagan]

*** This bug is a duplicate of bug 861848 ***
https://bugs.launchpad.net/bugs/861848


** Attachment added: /var/log/dpkg.log
   
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+attachment/2760771/+files/dpkg.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/936731

Title:
  pcmanfm crashed with SIGSEGV in __GI___libc_free()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/936731/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs