Confirmed, still happens on Ubuntu Gnome 16.04 too (using xfreerdp
2.0.0-dev)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/712702
Title:
xfreerdp stops responding to keyboard input for no apparent
In my case, this might have been caused by a hard disk in RAID1
operation failed, causing a degraded RAID array, in which /boot
apparently becomes read only in which case this is not a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Same issue here, on 12.04.5 LTS
even after Joseph's instructions (install -f, clean, and update), I
still get this:
user@server:~$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt-get -f install' to
The question mark has disappeared; don't know what changed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352975
Title:
GUI symbol for Wi-fi in 14.10 shows not connected even when connected
To
Confirmed on clean ubuntu gnome 14.10 install. Wifi radar is not
involved!
Happens on two independent Wifi networks
** Changed in: wifi-radar (Ubuntu)
Status: New = Confirmed
** Changed in: wifi-radar (Ubuntu)
Status: Confirmed = Invalid
** Changed in: network-manager (Ubuntu)
BTW, a question mark is also shown when using an ethernet connection
through a USB adapter, so it's not just WIFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1352975
Title:
GUI symbol for Wi-fi
Confirmed!
According to the strace output Inkscape is trying to find a file on an
unreachable sambashare, a file which is totally unrelated to Inkscape.
Clearing the recent file list helped
Running 12842 on Ubuntu 13.10
--
You received this bug notification because you are a member of Ubuntu
This bug is still present on Ubuntu 12.10 beta. I had to manually
install mesa-utils to get the driver type to be displayed on the details
tab. System is fully up-to-date, all available updates have been
installed!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Fixed also for Spyder (on up-to-date 12.10, 64 bit), thanks a lot!
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1005677
Title:
Re-emergence of Gtk-CRITICAL **:
Moved yesterday from 11.10 to 12.10 Beta (clean install), and
experienced this bug too. I can confirm that this affects the hplip
toolbox, but also Spyder (which is a python IDE).
The work-around in comment #5 is all that is needed to get spyder to run
properly:
LIBOVERLAY_SCROLLBAR=0 spyder
So
Been having this problem for years on my Shuttle SN78SH7 too (this model
has a nVidia GeForce 8200 chipset). In my setup just adding noapic to
the kernel boot option solves the problem.
BTW, I'm running Fedora 15 with kernel 2.6.42.3-2.fc15.x86_64, so this
is not Ubuntu specific. Also, I'm
This issue is rearing it's ugly head again in Oneiric:
diederik@diederik-desktop:~$ netgen
NETGEN-4.9.13
Developed at RWTH Aachen University, Germany
and Johannes Kepler University Linz, Austria
Including OpenCascade geometry kernel
Error in Tcl-Script:
result = couldn't read file ./ng.tcl: no
As of revision #9970, Inkscape starts blazingly fast again on my pc! So
this solves the boot slowness problem which was introduced somewhere
after the v0.47 release... but only for those who don't have thousands
of fonts installed, because only the icon rendering has been improved
See
Two things slow down Inkscape while it's starting up:
1) it's building a list of fonts: using a font manager to reduce the number of
fonts might help
2) it's rendering its own icons: improvements are planned
For more details see this thread:
Confirmed fixed on Fedora 12, using gtk2-2.18.6-1.fc12.x86_64
This GTK2 version was already installed on my PC as part of a regular
update on Jan. 17th, but I hadn't noticed this fix yet because I was
still running Inkscape using the workaround.
--
inkscape crashes using certain input methods:
Confirmed on Fedora 12 too, using today's revision of Inkscape
However, this does not work for me:
unset GTK_IM_MODULE inkscape
This did the trick though:
GTK_IM_MODULE=gtk-im-context-simple inkscape
--
inkscape crashes using certain input methods: _gdk_input_grab_pointer:
assertion
Hi Hope, we will need more information to be able to help you. For
example, which Inkscape version are you using? Have you tried our latest
prerelease yet? Which operating system are you using, XP, Mac, Linux?
Can you share a copy of your files with us such that we can try
reproducing this bug?
To JayK and Danny Staple: which version of inkscape are you using? v0.46
or a nightly development build?
If you're not already using the latter, then could you please try one?
Available here:
http://ubuntu.cafuego.net/dists/jaunty-cafuego/inkscape/
or here
*** This bug is a duplicate of bug 257685 ***
https://bugs.launchpad.net/bugs/257685
** This bug has been marked a duplicate of bug 257685
Inkscape color chooser widget's maximum limited to 245 instead of 255
--
Cannot set the maximum value in color selection
*** This bug is a duplicate of bug 257685 ***
https://bugs.launchpad.net/bugs/257685
There are a few things you can do if you find this annoying:
- wait for v0.47 to be released
- use a nightly build; however, these are not available for Gentoo AFAIK, so
you would have to compile your own
20 matches
Mail list logo
