Public bug reported:
error pop up will not remove itself even in upgrade
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
Uname: Linux 4.4.0-81-generic i686
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: i386
Date:
Possibly a duplicate of 1496558? I have a similar problem which has
continued onto Kubuntu 15.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1505391
Title:
Firefox 41.01 Constantl
Crashes continue, seemingly at random, in Firefox 41.
This crash occurred right after restarting Firefox after a previous crash,
without even reopening tabs.
https://crash-stats.mozilla.com/report/index/8755c238-76e3-4b86-92e2-ca33d2151019
--
You received this bug notification because you are a
Posted too soon. This happened when I was loading a Youtube page.
https://crash-stats.mozilla.com/report/index/c8082530-0a97-4bcb-9fda-0a51f2150926
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.
Crashes appear to have stopped since upgrading to Firefox 41.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1496558
Title:
Firefox crashes repeatedly with no apparent pattern
Status
Took the better part of two days, but the Mozilla release binary finally
crashed in a similar fashion. Crash report here: https://crash-
stats.mozilla.com/report/index/7f34b16b-a82f-43d8-8aef-a78982150921
Posting this here as well as on Bugzilla in case this is a bug in
another package causing Fir
It seems like this is a bug in the Ubuntu package since I have been
using the Mozilla release binary for a couple days now with no crashing,
including with the same ~/.mozilla/ directory and plugins.
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
Public bug reported:
I am not sure how to reproduce this bug, as the crashes seem to happen
at random, including at times I have left Firefox open and gone away
from my computer only to find it has crashed in my absence. I have a lot
of crash reports submitted, but there is no one thing I have fou
I chatted with the app owner of Rhythmbox about this. I was right about
my above patch fixing this bug but re-introducing a different bug. So
ignore that for fixing this.
He says a permanent fix was applied. So looks like Ubuntu's build
grabbed the wrong copy of Rhythmbox's source code. Looks to m
Looks like code that sets an encoding property when synching was removed
for the 2.98 version. Restoring it seems to fix the problem for me. I
attached a patch file for this. Just load this up and rebuild.
** Patch added: "rb-transfer-target.c.patch"
https://bugs.launchpad.net/ubuntu/+source/r
I want to note that the patch I loaded here probably re-introduces some
other bug, that this code was removed for a reason, so don't consider
this a suggestion for an official fix. But if it works around the
problem for you then feel free to use it until an official fix is found.
--
You received
Update form my last comment: looks like the timing with the Ubuntu
upgrade is coincidental. I downgraded Rhythmbox to a version that used
to work and still have the same problem. The cause seems to be if I
include my podcasts in the synch. If I uncheck that then it synchs fine,
no crash. Just so ha
Worked fine in Ubuntu 12.10 with Rhythmbox 2.97. Upgraded to 13.04 /
2.98 and now it crashes. iPod video 30 GB. Anyone found a way to
downgrade Rhythmbox to 2.97 on Ubuntu 13.04? That might be a workaround.
--
You received this bug notification because you are a member of Desktop
Packages, which
Not that it needs more confirming, but yeah, the killing of gvfsd-http
worked for me, too. If it's a bug in Rhythmbox itself then I'd be happy
to attempt a fix it if a maintainer or other expert in the source code
can give me pointers to get started. I was recently hacking the
Rhythmbox source, so
I don't know how it is created, but I think it is more about timing.
Perhaps SSH tries to get a file handle to ~/.pam_environment and run it
itself at a point in time after the encrypted home has been mounted,
whereas perhaps the normal LightDM session login does so too early.
--
You received thi
I confirmed that the above work-around (adding session required
pam_env.so to /etc/pam.d/common-session) works great. Perhaps that's all
Ubuntu needs to do to fix this bug? Not sure if there are any negative
side effects, but so far I'm not experiencing any.
--
You received this bug notification
*** This bug is a duplicate of bug 952185 ***
https://bugs.launchpad.net/bugs/952185
Looks like this is a dupe of 584249. There's a workaround in that one
that worked for me:
session required pam_env.so
Add that line at the end of /etc/pam.d/common-session is supposed to
force it to read the
Looks like this is a dupe of 584249. There's a workaround in that one,
though I haven't tested it myself yet:
session required pam_env.so
Add that line at the end of /etc/pam.d/common-session is supposed to
force it to read the ~/.pam_environment afteram encrypted $HOME is
mounted.
--
You recei
Anyone have a workaround for this?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/952185
Title:
~/.pam_environment not parsed when HOME is encrypted
Status in Light Display Manager:
** Attachment added: "/etc/default/keyboard"
https://bugs.launchpad.net/bugs/1027448/+attachment/3231137/+files/keyboard
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1027448
Title:
Public bug reported:
My /etc/default/keyboard file (attached) has this:
XKBOPTIONS="compose:ralt
The XKBOPTIONS line allowed me to use the compose key in the LightDM
password entry box so I could have a more secure password. It was
working fine. But a recent update came through and now the compos
21 matches
Mail list logo
