hmm ... looking at that site lmdb 0.9.24 seems to be in stable . I
guest that is as good as it gets.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lmdb in Ubuntu.
https://bugs.launchpad.net/bugs/1995416
Title:
lmdb is out of
Public bug reported:
Subject says it all. Is it possible to report out-of-date packages in
another way that a bugreport ?
** Affects: lmdb (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is
I see the same behavior.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1905467
Title:
[USB-Audio - Logitech Wireless Headset, playback] volume slider -
sound audible only from
Happens to me as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1572244
Title:
Kubuntu requires that the WiFi password be entered twice before WiFi
can be used
Eduards - that is most likely a different issue. If you look closer you
will probably find that your network is not even listed in the
networklist. This bugreport is about systems that do not reconnect even
when the network is listed.
--
You received this bug notification because you are a
I have had no problems for a very long time.
--
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/927065
Title:
Firefox 10.0 crashes when visiting a website with a java applet
Status in
But #13 is not a solution - it's a workaround.
I changed to Debian becasue of this bug. I've never looked back. The bug
has been present for 5 months now.
Btw. is this still occurring in the current 15.04? If it is and it's not
fixed for the release this bug has potential to be present until
Please try #51 also
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not autoconnect to wireless network
Status in network-manager package
@tobiasBora: YEs only for the current session. But that something every
fix has in common - except for the Allow all users to access this
network-option.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
As state in a previous post: You can change whatever setting you'd like.
It does not have to be the auto-connection setting. You can even
change the IP-allocation policy from DHCP to Manual.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
The spelling is bad in #32 but the essence is that the problem persists
on Unity, so it is not a desktop related problem (KDE, Unity, etc)
The later comments just state that Debian Unstable works, and since
Ubuntu is based on Debian Unstable that might help people tracking down
what's wrong.
--
I take my previous comment back. Debian unstable also does this.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not autoconnect to wireless
Debian actually does not have this problem after all. does that help
anything?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not
FWIT it works in debian unable
network-manager 0.9.10.0-3
plasma-nm0.9.3.4-2
plasma-widget-networkmanagement 0.9.3.4-2
--
You received this bug notification because you are a
I'll try it out today.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not autoconnect to wireless network
Status in “network-manager”
Ok - these are the facts while trying out Ubuntu 14.10. I did not try
Kubuntu 14.10 from USB because the steps below results in the exact same
weirdnesses on the Kubuntu 14.10 install I have,
1. Create boot disk - reserve 1GB for storage.
2. Boot the from USB
3. Setup wifi - it connects.
4.
Hervé - you are right. I works as a software developer and this bug
would clearly be a blocker - meaning that we cannot realease until it's
resolved. Simple John Joe tpye of things must always work. I know little
of any about networkmanager, but given the right instructions I'd be
able to debug
I can not see that file on my system.
I have these files.
-rwxr-xr-x 1 root root 549 Jan 18 2013 000resolvconf
-rwxr-xr-x 1 root root 881 Dec 30 2013 avahi-autoipd
-rwxr-xr-x 1 root root 484 Dec 30 2013 avahi-daemon
-rwxr-xr-x 1 root root 1675 Jan 28 2014 ethtool
-rwxr-xr-x 1 root root
To sum up.
1. New connections always reconnect.
2. After reboot connections does NOT reconnect.
3. Allowing all users to connect makes auto-connection work even after reboot.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
That makes me happy and sad at the same time. Happy because this bug is really
annoying and maybe it can get some attention, and sad because it's present in
14.10 and potentially a lot of users will now end up fight to get wireless
connecting.
--
You received this bug notification because you
I can add that flipping ipv5 setting to ignore and then back to
automatic makes auto connection work again. I do think that it is
needed for every reboot though. But it's a workaround.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Do you have a possibility to try kubuntu 14.10 installed from scratch.
Maybe some upgrade-path related issue is at stake here.
Also - I think this _must_ be resolved for 14.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Could you please check that the audio-setup in system-setting looks
alright (the correct name of the detected devices etc.). I remember
someone on IRC telling me that it had something to do with that. But
then again I might be wrong...
--
You received this bug notification because you are a
I believe that should be alright. As long as the audio-setup dialog does
not change appearance with the change it's ok. Alternatively I'll report
back if I notice any changes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
I reopened the bug since it's still present. My comment above is still
valid, but auto connecting stops working when suspending to ram or
rebooting. So basically the desired behavior can be obtained temporarily
by removing and adding the network in question.
** Changed in: network-manager
After getting KDE 4.14 I tired to remove all the wifi connections and
add them again. Now everything seems to be alright.
** Changed in: network-manager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Do you have any good ideas as to what I could try out to figure out
what's wrong?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1354924
Title:
Networkmanager does not
Works on current 14.10 also. Good job juanmanuel !!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device
Public bug reported:
When adding a net wireless network and enable connect automatically'
networkmanager does not automatically connect to the network wenever
possible.
I'm running kubuntu 14.10 daily.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: network-manager 0.9.8.8-0ubuntu23
Pulseaudio and KDE aside.
What is aplay doing the the KDE-startup sequence in the first place?
I know theres a login sound, but should'nt that be played by some application
through pulseaudio directly.?
--
You received this bug notification because you are a member of Desktop
Packages, which
Did you see my systemtao log of a KDE login from a cold reboot.
https://launchpadlibrarian.net/172625307/kde-login.stap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
I've reported no other bugs. Basically this report was done in a rush
because shipping 35 in 14.04 was wrong in the first place IMHO.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Any news on this. It should be faily easy to downgrade to 33 or
something.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1307717
Title:
multiple problems with new
A better way
Download file from here https://launchpad.net/~canonical-chromium-
builds/+archive/stage/+build/5815874
https://launchpad.net/~canonical-chromium-builds/+archive/stage/+build/5815874/+files/chromium-browser-l10n_33.0.1750.152-0ubuntu1~pkg995.1_all.deb
Upgrading does not help. The problem is that 14.04 is shipped with a
version that has been en the repositories for 3-4 days. M34 landed there
this monday and the release was thursday. NPAPI has apparently been
scrapped in M34. As I wrote before in this bug chromium should be rolled
back to M33
icedtea does not work because NPAPI was dropped in 34. It will happen no
matter what we do, but pulling it into 14.04 3 days before release is
not the way to do it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
Please roll back to the previous version before the release tomorrow.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1307717
Title:
multiple problems with new
Theres another thing. It fails to detect the installed icedtea-plugin
package. So Java is broken in it too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1307717
Title:
** Description changed:
Hi
Chromium-browser was just updated and there are multiple problems with
it.
- First of all the font size in the address line is too huge.
+ * icedtea-plugin not detected.
+ * pepper seems to be the only API supported now.
+ * Maximizing/normalizing the window
Come on. Release is in a few hours. Roll back to
33.0.1750.152-0ubuntu1~pkg995.1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1307717
Title:
multiple problems with new
Yeah - might be an idea to not include multiple things, but release is
in 48 hours and I would not like to see this bug in trusty. Actually I
thing the best way ot go is to roll back to the previous version.
Anywya dconf says nothing. The response in the command line is empty.
--
You received
Am I the only one that cares for this bug. Unfortunately I'm unable to
figure out why aplau trigger pulseaudio to that more times. And release
is in 48 hours or so.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-plugins in Ubuntu.
Public bug reported:
Hi
Chromium-browser was just updates and there are multiple problems with
it.
First of all the font size in the address line is too huge.
Secondsly when maximizing/normalizing the window the top right part of
the window is not redrawn.
ProblemType: Bug
DistroRelease:
** Description changed:
Hi
- Chromium-browser was just updates and there are multiple problems with
+ Chromium-browser was just updated and there are multiple problems with
it.
First of all the font size in the address line is too huge.
Secondsly when maximizing/normalizing the
*** This bug is a duplicate of bug 1296425 ***
https://bugs.launchpad.net/bugs/1296425
** This bug has been marked a duplicate of bug 1296425
pulseaudio is started twice - effectively making device management
impossible.
--
You received this bug notification because you are a member of
Heres a log on a KDE startup and as far as I can see it is a cascade
looking something like this.
DriverManager start python3 which then starts aplay which then again starts
pulseaudio. Parallel to that kmixctl is also starting pulseaudio. Both lines of
events happen 2 or 3 times. They sort of
Another thing. The *first* pulseaudio is the instance that works and
respawns if killed. So kmixctl is from my perspective allowed to start
pulseaudio aplay is not.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
ok - chmod -x /usr/bin/aplay solves it. Now that aplay does not run
pulseaudio no additional instances is run.
Now the question is why aplay runs pulseaudio.
Lokking the the alsa-repositories I found the following
* alsa-utils - nothing interesting.
* alsa-lib - nothing interesting.
*
Public bug reported:
When starting up libreoffice (it does not matter which component) the
screen is no redrawn and the window does not react to close event and
needs to be killed to quit.
I have not much more info than this except that I have tried deleting
the configuration and got the same
Is anything happening with this bug. I'll be happy to recompile anything
to help tracking this down.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is
As far as I remember it was solved in pl2303 kernel driver. Please
correct me if I'm wrong.
** Changed in: modemmanager (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in
It's no longer a problem.
** Changed in: usb-modeswitch (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: usb-modeswitch
Status: New = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in
I beleive that total stack has proper support for this now.
** Changed in: xserver-xorg-input-evdev (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu.
The issue is also present when running the latest cd-image in
virtualbox.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively
It does not happend in Unity - only KDE.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1296425
Title:
pulseaudio is started twice - effectively making device management
Public bug reported:
Quote from this post. :
http://linuxadvantage.blogspot.dk/2013/01/kde-rather-slow-to-start-pulseaudio.html
On many distributions delivering KDE, since version 4.2, I have often
found incomprehensibles slowness between login step and the time the
desktop is fully loaded and
Public bug reported:
On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system)
pulseaudio is running twice. This makes attaching/deattaching of usb-headset
and other stuff impossible because the two instances fight ove rthe events.
Tow reproduce just boot up the current image
I can add that it is the first instance started that is the correct one.
Shutting that doesn will make it respawn. That is not the case for the
second instance.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
This is as far as I can see not an upstream bug, but merely a versioning
issue.
usb-modeswitch depends on usb-modeswitch-data = 20110227-1~, but it
turns out that usb-modeswitch-data's version is in fact 20131113-1. But
I'm guessing that that the ending ~ might trick the package management
Latest upstream usb-modeswitch-data is this :
http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-2.0.1.tar.bz2
http://www.draisberghof.de/usb_modeswitch/usb-modeswitch-data-20131113.tar.bz2
So I guess usb.modeswitch and usb-modeswitch-data should both be updated
to more recent version.
--
Well, this still happenens in kubuntu 14.04 daily running in virtual-
box.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
Title:
When selecting two cell and draggin them X locks
Public bug reported:
After login into KDE skype is started up automatically. Everything seem ok -
except that sound output does not work until restarting skype. This goes for
every login - event if I ensure that skype does not startup automatically. I
always need 2 startups to get audio
** Description changed:
+ After login into KDE skype is started up automatically. Everything seems
+ ok - except that sound output does not work until i restart skype. This
+ goes for every login. If I on the other hand ensure that skype does not
+ startup automatically audio output will work
This is not present in the daily build so I guess a reinstall is the way
to go. Still - I wonder what might be wrong with my system. It is
installed as 12.10 and upgraded through development of 13.04 and 13.10.
** Changed in: upower (Ubuntu)
Status: New = Invalid
--
You received this bug
Well - forget all about my local system. It does still happen within
VirtualBox running current saucy daily dail.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
Title:
When
apport information
** Tags added: apport-collected has-fix has-workaround kubuntu
reproducible saucy single-occurrence
** Description changed:
Steps to reproduce :
1. Start libreoffice-calc
2. Select 2 cells
3. Try to draw the cells to another location
Actual result:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839438/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839443/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839442/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839441/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839440/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839439/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839444/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839448/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839450/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839455/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839451/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839454/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839437/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
It works now on my local saucy install - but the daily-build still fails
the same way. Maybe the daily build is not updated yet. I will return
again with more information when the daily build has been updated.
--
You received this bug notification because you are a member of Desktop
Packages,
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839456/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839447/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839452/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839453/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839449/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839457/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839445/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1228587/+attachment/3839446/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1228587
This is still present in current 13.10. Is upower the correct package
for this bug. I suspect that it isn't.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1185165
Title:
KDE does not
Public bug reported:
Steps to reproduce :
1. Start libreoffice-calc
2. Select 2 cells
3. Try to draw the cells to another location
Actual result:
The mouse cursor locks and nothing more happenens.
Changing back and forth between tty1 and X a couple of times solves the lockup.
Expected
Hmmm ... where is that commit I can't find it in linus' kernel
tree.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1184867
Title:
Xorg crashed with intel_dri
Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1184867
Title:
Xorg crashed with intel_dri backtrace whil attending a google hangout
Status in
Public bug reported:
Basically I just enter a hangout and then after a while - 30 seconds or so -
the system crashes with this backtrace
[ 432.229] (EE)
[ 432.230] (EE) Backtrace:
[ 432.250] (EE) 0: /usr/bin/X (xorg_backtrace+0x49) [0xb7751f99]
[ 432.258] (EE) 1: /usr/bin/X
Public bug reported:
My KDE installation does not show a suspend-to-ram option in the shutdown menu.
/sys/power/state contains freeze mem disk
Writing mem to /sys/power/state actually suspends the system.
This might not be a upower issue, please change that if I', wrong.
ProblemType: Bug
Public bug reported:
I was running a git gc command, when suddenly Xorg crashed
The trace smells like a memory allocation problem.
[ 2231.463] (EE) intel(0): Failed to submit batch buffer, expect rendering
corruption or even a frozen display: No space left on device.
[ 2231.467] (EE)
[
It also happenens with krunner and the kde system monitor
--
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/951725
Title:
Black Background
Status in “firefox” package in Ubuntu:
http://www.kubuntuforums.net/showthread.php?57753-Firefox-and-
Thunderbird-Black-Background
quote ronw
Another me too reply. My current workaround is to start Nvidia Settings,
which is also mainly black. As I click on things inside the Nvidia Settings and
move the mouse around, the various
The nvidia-trick actually works :)
--
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/951725
Title:
Black Background
Status in “firefox” package in Ubuntu:
Confirmed
Bug description:
Works for me too.
--
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/927065
Title:
Firefox 10.0 crashes when visiting a website with a java applet
Status in “firefox” package in Ubuntu:
I'm experiencing the same. A fresh 12.04 live-cd session also crashes.
--
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/928843
Title:
Firefox crashes on loading a Jmol applet
Status
1 - 100 of 101 matches
Mail list logo
