Another eGroupware user found a way to fix the PostgreSQL search bug, so
basically all the information needed to patch these bugs now exists. See
http://forum.ebox-platform.com/index.php?topic=2470.msg15582#msg15582
--
eGroupware ProjectManager doesn't work properly with PostgreSQL
https://bugs.l
IMO this should be above "wishlist" importance, because the lcdproc
project had to disable a lot of display drivers (such as
hd44780-lcd2usb) still relying on libusb 0.1 API, while libusb-
compat-0.1 probably would've solved their issues easily. An LCD that
worked perfectly with Ubuntu 16.04 is now
This issue affects other applications as well, such as Pidgin with Perl
plugins segfaulting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897561
Title:
libperl.so.5.30.0 causes nginx to segfault
I don't know if this is directly related, but after upgrading to Ubuntu
14.04 and XBMC 13 (Gotham) beta on a touchscreen computer (Asus EeeTop,
IDC 6681 touchscreen), XBMC went all crazy. It behaved as if someone was
holding down an arrow key, with focus jumping between elements and the
associated
I was plagued by this problem for a long time (probably since 9.04),
until I got fed up, opened my laptop and disconnected its touchpad
permanently (I prefer a mouse anyway). That fixed the problem for me,
but this is not something I'd recommend others to do, especially since
there's often a switch
I worked around this bug by adding a .desktop file for xdg-open and then
setting it to be the default handler for unknown binary (application
/octet-stream) files. It appears as "Let Ubuntu choose" in Firefox for
opening files. I haven't had any problems since.
1. Put the below lines into a new f
Here's info for Acer Aspire 8530G (AMD HD3200 + HD4650)
** Attachment added: "Acer-Aspire_8530.tar.gz"
https://bugs.launchpad.net/lpbugreporter/+bug/752542/+attachment/4321793/+files/Acer-Aspire_8530.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
I tried installing from two different USB sticks on two different
computers, multiple times, and all hardware has been tested to work, so
this is probably not a real disk error. The same error condition happens
every time, towards the end of the setup process.
The installed U
** Description changed:
I tried installing from two different USB sticks on two different
computers, multiple times, and all hardware has been tested to work, so
this is probably not a real disk error. The same error condition happens
every time, towards the end of the setup process.
@psusi: I checked the sticks, and they both show errors. They're both
new and of different brands (Kingston and Transcend) and sizes, so it
seems quite unlikely that both are just randomly broken. Perhaps this is
a bug in Startup Disk Creator instead? Doesn't it do any data
verification?
--
You r
The ISO is OK, as I burned it to a DVD and it installed fine. Also, I
tried recreating both sticks several times, and got no I/O errors until
Ubiquity tried to install from them. I wouldn't have reported this if it
hadn't happened 10 times or so.
--
You received this bug notification because you
OK, looks like I had two ISO files all the time. One of them fails MD5
check, so perhaps that was the one Startup Disk Creator kept writing to
the USB drives. Apparently mistakes start happening after 2 weeks of
ridding the world of XP.
--
You received this bug notification because you are a memb
I noticed this error on 10.04 LTS when trying to run gnome-about-me.
Like Dan Swift I have upgraded Evolution to 2.32 (with a PPA), but I'm
not sure if that caused it, since I seldom use gnome-about-me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I was testing Natty on an Asus Eee Top (IDEACOM IDC 6681 touch screen)
and came across this bug. The utouch-team/unstable PPA seems to fix the
buggy touch screen behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I'm surprised I haven't found this bug report until now, despite many,
many days of enraged googling. My HP/Compaq 6720s turned into a nuisance
somewhere around Ubuntu 9.xx versions, when this issue popped up along
with (possibly somewhat related) touchpad/mouse bugs #362359 and/or
#375905.
Actual
If I recall correctly, this happened to me when upgrading from 10.04 to
10.10, but was easily fixed with gconf-editor by setting desktop\gnome
\url-handlers\ftp. Once again the upgrade from 10.10 to 11.04 broke FTP
bookmarks, but this time editing the configuration doesn't help; that
gconf value is
I found a workaround for the FTP part of the problem, but someone should
confirm if it works for others too.
After running this command, FTP bookmarks open in Nautilus instead of
Firefox, both in Unity and Classic:
xdg-mime default nautilus.desktop x-scheme-handler/ftp
--
You received this bug
I noticed that the xdg-mime workaround (see #8) worked on one computer
but not others, so it was probably just a lucky side effect from some
other workarounds I've tried.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
OK, so apparently desktop\gnome\url-handlers\ftp in my gconf is just a
leftover from Maverick and no longer works (in reply to #5).
Since this affects not only Unity but Gnome too, shouldn't this bug be
filed against a package package other than unity in order to get proper
attention?
--
You rec
I still experience this in Maverick, with applications which can be
minimized to tray, such as Pidgin and Gwibber. I've struggled with more
show-stopping display bugs, so I haven't really followed if this
particular behaviour has remained unchanged through 8.xx and 9.xx
versions.
Unlike described
It may have been too early to mark this invalid. Yesterday I did a clean
install (although later restored my old home folder) of Maverick beta,
and a moment ago I noticed that my left speaker is now dead, just like
in this bug description. This is not a hardware issue, because
everything worked fin
Some more information: Headphone output provides proper stereo audio
despite the speaker problems, so my guess would be that this is a sound
driver bug, not a Pulseaudio glitch. Apt logs indicate that many ALSA-
related packages were updated right after I installed 10.10.
--
[VIA VT1828S] Only ge
OK, this is weird: My speakers started working again, even though I
don't think I changed anything that might have caused it. Maybe this is
a random hardware bug after all. That would explain why others haven't
come across it.
--
[VIA VT1828S] Only getting mono sound with 10.10
https://bugs.launc
23 matches
Mail list logo
