Public bug reported:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmod 400 ~/.ICEauthority
- rm ~/.ICEauthority
In this scenario, the user is returned to t
I can do that if really required, but this is not a bug with my system -
it's just the way the system works right now, so I'm suggesting an idea
for how we can make it better :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
apport info added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1800277/+attachment/5206696/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Tags added: apport-collected bionic
** Description changed:
= Problem =
It is too easy to make a system unusable.
= Examples
The following commands will all cause subsequent graphical logins to
fail:
== User is returned to login screen ==
- chmo
Reported as https://gitlab.gnome.org/GNOME/gdm/issues/438.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800277
Title:
"chmod u-w ~/.ICEauthority" breaks login
To manage notifications about this b
*** This bug is a duplicate of bug 1235649 ***
https://bugs.launchpad.net/bugs/1235649
** This bug has been marked a duplicate of bug 1235649
uevent spam causes libdbus client code in session upstart to consume massive
amounts of memory on Ubuntu Touch
--
You received this bug notificati
scp suffers the same issue, but interestingly, so seemingly does pscp
which hangs indefinitely after successfully connecting and starting to
send the data.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
We need a proper stack trace to aid debugging this issue. So, if you
have seen this bug please run the following:
$ apport-collect 1222705
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222705
Title:
This is very odd - #3 suggests the failure is in the auto-generated
D-Bus binding code.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1255569
Title:
session-init-less session-init session
To manage
Hi Anatoly - thanks for reporting this issue. Presumably, lightdm
started correctly before you noticed this issue?
If the process is still running, please do:
sudo cat /proc/$(pidof initctl)/stack > /tmp/initctl.stack
... and attach "/tmp/initctl.stack" to this bug. Then, to stop initctl
(by for
** Branch linked: lp:~jamesodhunt/upstart/bug-530779
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/530779
Title:
init: does not wait for parent to exit when following forks
To manage notifications
= Issue =
If the install was performed specifying "console=", then the installer
would have attempted to create a suitable Upstart job for that device.
= Installer File =
The file to consider is:
http://bazaar.launchpad.net/~ubuntu-installer/finish-
install/master/view/head:/finish-install.
Hi Anatoly - do you now have a /var/crash/_sbin_initctl.0.crash file? If
so, please attach it to this bug so we can investigate.
Not that my instructions in comment #2 would have both quietened your
CPU and provided us with the required debug we need to investigate this
issue further.
--
You rec
Hi Daniel - A couple of initial questions...
1) Has this problem just started? If so, what changed?
2) How far into the boot does it get?
Can you try removing "splash" and "quiet" from the boot command-line.
Also, you could try copying tty8.conf from
http://people.canonical.com/~jhunt/upstart/co
Problem is caused by UPSTART_JOB and UPSTART_INSTANCE still being set in
the gnome-session environment.
** Project changed: upstart => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
** Attachment added: "Updated /usr/share/upstart/sessions/gnome-session.conf
th
This is not a bug: the failsafe job detects if the system failed to boot
and takes appropriate action. However, in all likelihood your system
will boot as expected so the failsafe job (which is always started) is
stopped. Upstart does this by sending the TERM signal, hence the message
which can be
** Changed in: upstart (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324096
Title:
dbus call needed to set multiple environment variables in a single
Public bug reported:
Equivalent patch to [1] for sbuild.
[1] -
https://code.launchpad.net/~jamesodhunt/ubuntu/utopic/pbuilder/dep8-fix/+merge/221848
Debdiff since sbuild's bzr branch is OUT-OF-DATE.
** Affects: sbuild (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "sb
** Changed in: upstart
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
** Description changed:
Occurred immediately after bug 1222702 happened.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: upstart 1.10-0ubuntu1 [modified:
usr/share/upstart/sessions/upstart-file-bridge.conf]
ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
Uname: L
Hi Thibaut - Thanks for reporting this. I can recreate the problem
locally so the next update should resolve this issue.
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Summary changed:
- upstart-file-bridge 'EVENT=create' not working
+ upstart-file-bridge 'EVENT=create' not working for directories
** Changed in: upstart (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Found whilst investigating bug 1221466
** Information type changed from Private to Public
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
** Branch linked: lp:~jamesodhunt/upstart/bug-1221466+1222702
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222702
Title:
upstart-file-bridge assert failure: upstart-file-bridge.c:1162:
Assertion
** Branch linked: lp:~jamesodhunt/upstart/bug-1221466+1222702
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221466
Title:
upstart-file-bridge 'EVENT=create' not working for directories
To manage n
Latest kernel panic (from 2nd-level guest) using following kernel
versions:
host: 3.11.0-1-generic (-2 causes problems for my graphics hardware atm)
1st-level guest: 3.11.0-2-generic
2nd-level guest: 3.11.0-2-generic
** Attachment added: "kvm.log"
https://bugs.launchpad.net/ubuntu/+source/li
The latest advice for running on Canonistack (kvm guest instance where
nested=Y is to):
- Only run on a 64-bit Canonistack guest instance.
- Modify bin/prepare-testbed and bin/run-adt-test to start the autopkgtest VM
using 'qemu-system-x86_64 -enable-kvm'.
- Have the DEP8 test running inside the
'qemu -serial file:/tmp/kvm.log' Looks like an alternative to 'qemu
-nographic >/tmp/kvm.log 2>&1'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-
Re #27, removing -nographic still causes the same lockup for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208455
Title:
general protection fault running apt-get inside double nested kvm VM
To
Thanks Huubb - the encoded core files are still shown as belonging to
chrome so I'm not sure what is happening here. And until we have either
a stacktrace or a core file from init itself, it's going to be difficult
to determine the cause of this issue.
If anyone has this problem and does not have
Can you confirm that you are talking about PID 1? How are you checking
the amount of memory init is using?
Also, do you have a /var/log/upstart/ directory on your system?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Hi Leonardo - no problem. Can you check to ensure you have a
~/.cache/upstart/ directory (or "$XDG_CACHE_HOME/upstart/" if you have
manually set XDG_CACHE_HOME). Also, is the session init process
consuming a lot of CPU ("top -b -n1")?
--
You received this bug notification because you are a member
Sounds like bug 861268.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311488
Title:
Missing letters
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-g
Hi Huubb,
Thanks for this information. This is still very curious since according
to your /var/crash/, Upstart did seemingly crash, but on a different day
to chrome (chromium) crashing. Also, the upstart crash file seems to
have been uploaded before the crash occurred. That might be because
you've
Hi Huubb,
Thanks again. However, please can you attach
/var/crash/_sbin_init.0.crash as it doesn't appear in 'out'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300235
Title:
init crashed with SI
*** This bug is a duplicate of bug 901038 ***
https://bugs.launchpad.net/bugs/901038
Hi Serge,
The problem I believe is that Upstart is in the process of restarting so
initctl cannot (yet) reconnect to Upstart until it has finished the re-
exec. See comment #7 on bug 901038.
** This bug has
** Package changed: upstart (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300144
Title:
Requested shutdown results in Reboot
To manage notifications about this bug go to
Hit it again, and again it is triggered by firefox.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300722
Title:
hud-service is eating up 100% of one of my CPUs in a poll loop
To manage notificatio
Correct.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1300722
Title:
hud-service is eating up 100% of one of my CPUs in a poll loop
To manage notifications about this bug go to:
https://bugs.launc
Hi Michał - yes, it seems to be the same issue as bug #1222705. What is
new is the fact that we now know the call site so tracking down a proper
fix should now be easier. Looks like the issue is related to the initctl
set-env functions, which only affect Session Inits.
--
You received this bug no
Hi Joseph - in the past few days created a script to show a pop up when
I get any kernel oopses and that is what caused me to raise the bug.
However, checking my logs the earliest occurrence I have is from April
21 with same kernel version (3.13.0-24-generic):
Apr 21 18:10:09 faire kernel: [ 5637
Had 2 further cases of this in the last couple of days. What's
interesting though is that I now have a script that monitors for CPU
hogs. The script correctly detected hud-service spinning... *but* after
a period of time (<1m), it stopped spinning. Attached is the log fwiw.
** Attachment added: "h
Is your disk full? Does the memory drop down when you run 'start re-
exec'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321204
Title:
upstart (session) consumes almost 3GB of memory after 24 hour
Since the re-exec makes the memory drop down, this sounds like an issue
similar to bug 1235649 - a rogue client is connecting to upstart but
without using a main loop, or not registering the required NIH main loop
callbacks to allow libdbus linked into Upstart to flush the messages it
is attempting
Public bug reported:
This happens frequently (I have a script that monitors CPU usage).
$ top -b -n1 | head
top - 07:44:06 up 30 min, 3 users, load average: 1.35, 1.08, 0.82
Tasks: 329 total, 2 running, 327 sleeping, 0 stopped, 0 zombie
%Cpu(s): 17.4 us, 1.6 sy, 0.4 ni, 80.1 id, 0.5 wa
Looks like this might be being caused by flashplugin. After closing a
few tabs the problem is no longer recreatable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321602
Title:
chromium browser che
After performing a few tests, the problem seems to be that if a tab
using youtube's html5 player exists at browser start, chromium will spin
@ 100% cpu. Closing that tab makes the cpu usage drop to normal levels.
What is odd is that if no youtube html5 tab exists at startup and I then
create a new
Problem no longer occurs running kernel 3.15.0-1-generic.
** Changed in: linux (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/1319141
Title:
[Lenovo Thi
Public bug reported:
An unprivileged call to lxc-attach fails with kernel 3.15.0.1.2, but
works fine using 3.13.0-24-generic.
Under 3.15.0.1.2, attempting to connect to a running unprivileged
container:
$ lxc-attach --clear-env -n trusty -- /bin/true
lxc-attach: Permission denied - Could not ope
Public bug reported:
Package maintainer scripts often call:
invoke-rc.d $service restart
... to ensure that if a service is running, it gets restarted after
upgrade. invoke-rc.d is a SysV tool and the premise here is that calling
/etc/init.d/$service will be a NOP if the service in question
** Changed in: upstart (Ubuntu)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu)
Status: New => In Progress
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
This issue does appear to have been exposed by a change to Upstart:
Upstart now resets the terminal attributes for /dev/console to ensure a
sane environment for Upstart itself to operate in. It does this (and
*should* do this) since it cannot know what state the initramfs left the
console in (in fa
This is rather curious as /var/log/upstart is auto-created on install:
dpkg -L upstart|grep /var/log/upstart
I suspect something else on those systems is removing /var/log/upstart/
which is causing subsequent logrotate runs to error.
--
You received this bug notification because you are a mem
At long last, I can now recreate this problem at will.
Although I haven't debugged the actual cause yet (and hence don't yet
have a fix), it is triggered when the following occur "very close
together":
plymouth show-splash
plymouth quit
Note that the problem can occur on boot (where plym
One other point to note - this problem only seems to occur if using the
"script" splash plugin (which Ubuntu uses).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/553745
Title:
plymouthd crashed with
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
*** This bug is a duplicate of bug 553745 ***
https://bugs.launchpad.net/bugs/553745
** This bug is no longer a duplicate of bug 849414
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
** This bug has been marked a duplicate of bug 553745
plymouthd crashed with S
1 - 100 of 1868 matches
Mail list logo
