It is nearly impossible to know what the OpenCL programs require
specifically. E.g., I did some testing and boinc-amd-opencl seems to
work with the ICD loader by ocl-icd-libopencl1 but not with the specific
one by fglrx; on the contrary, oclHashcat needs the specific
libOpenCL.so.1 by fglrx but
That is the problem: There should be only one loader but there are two
of them. fglrx at least (I ignore what is the case for nvidia) provides
its own at /usr/lib/libOpenCL.so.1 and this conflicts with the one by
ocl-icd-libopencl1 that goes to /usr/lib/x86_64-linux-
gnu/libOpenCL.so.1. Both are
It is still not fixed for me: If we do not explicitly provide
libopencl1, wine still requires ocl-icd-libopencl1 which installs a
conflicting libOpenCL.so
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1482844 ***
https://bugs.launchpad.net/bugs/1482844
** This bug has been marked a duplicate of bug 1482844
Caffeine can't connect to display since updating Trusty to Vivid kernel and
X (HWE)
--
You received this bug notification because you are a
Even with these upgraded versions I keep getting:
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc0 in position 0:
invalid start byte
Version 0.14+20091101-5 which is currently in debian unstable
(https://packages.debian.org/sid/python3-xlib) solved this.
--
You received this bug
** This bug is no longer a duplicate of bug 1206371
libhybris breaks mesa (cannot find libwayland-egl.so.1)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270960
Title:
totem fails to open
I do not have libhybris and I have never installed it. It is obviously a
separate issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270960
Title:
totem fails to open unable to load to
mc0e, as previously mentioned, a somewhat more canonical workaround is
using g-s-d's hotplug-command script (see the hotplug-input-device.sh
attachment to this bug). This has the advantage that it works not only
at startup but also after suspend/resume and if the device is
hotplugged.
--
You
*** This bug is a duplicate of bug 1247221 ***
https://bugs.launchpad.net/bugs/1247221
** This bug has been marked a duplicate of bug 1247221
Nautilus doesn't remember setting for showing hidden files correctly when
org.gtk.Settings.FileChooser show-hidden is true
--
You received this
*** This bug is a duplicate of bug 592842 ***
https://bugs.launchpad.net/bugs/592842
** This bug has been marked a duplicate of bug 592842
appmenu doesn't work with apps run as sudo root
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Stéphane, until that arkose2, do you know of any equivalent alternative?
I mean for quick non-persistent sandboxing (e.g., for build testing)
above a bare lxc.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have finally upgraded to trusty: no more systrays.
In consequence, I am sadly back to tomboy, which does have a well
integrated indicator.
Only workaround so far: Install tomboy, manually import every note,
remove gnote
--
You received this bug notification because you are a member of Ubuntu
Well, Notify OSD is synchronous for system volume and screen brightness.
Then, why does core ubuntu functionality go against the standard?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390508
Title:
*** This bug is a duplicate of bug 724856 ***
https://bugs.launchpad.net/bugs/724856
I see this issue reappearing for me in precise. I have 3 remote
calendars (google and zimbra) and restarting indicator-datetime makes
the calendar reappear.
Most interestingly, this exact same setup did not
At least in my case, what happens is that .Xauthority is owned by root
after running startx (as root). A workaround:
sudo rm ~/.Xauthority
I am not sure to which extent this constitutes a bug, though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 780602 ***
https://bugs.launchpad.net/bugs/780602
Aaron, this bug has been fixed in a recent update. Maybe you are
experiencing bug #1011073 which is fixed in precise-proposed and the fix
should be in updates soon.
--
You received this bug notification
Me I also use a few legacy programs that need the notification area. My
workaround (not mentioned yet): gnome-panel, with the notification
area applet.
I use a single, very small, non-expanded panel with this and other
applets I still use (invest applet, classic menu, and window selector)
in an
I followed the logic that I commented. I see it is not something about
the cups-pdf package. Sorry for the entropy
** No longer affects: cups-pdf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 457221 ***
https://bugs.launchpad.net/bugs/457221
Thanks to your diagnosis Brian I see it has already reported as #457221
so I mark this bug as duplicate
** This bug has been marked a duplicate of bug 457221
cups-pdf always classed as OBSOLETE and
As pointed out by brian-murray in Bug #987026 cups-pdf is obsoleted in
DistUpgrade.cfg
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/987026/comments/7
** Package changed: update-manager (Ubuntu) = ubuntu-release-upgrader (Ubuntu)
--
You received this bug notification
** Also affects: cups-pdf
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987026
Title:
cups-pdf package removed at each ubuntu version upgrade
To manage
update-manager updates correctly for any other package. This indicates
that there is something specific in the way cups-pdf is packaged that
blocks its update
** Project changed: cups-pdf = cups-pdf (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
You do not need the closed-source Google Chrome just to run its Flash
plugin. It is also available in Chromium:
chromium --ppapi-flash-path=libpepflashplayer.so --ppapi-flash-
version=VERSION
You can extract the libpepflashplayer.so from chrome package. E.g., first
download
** Changed in: ubuntu
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/672658
Title:
Loosing the dash character (–) after conversion.
To manage notifications about this
Workarounds #59 and #67 work for me until I suspend / resume.
The canonical solution is to run the xinput commands (or their synclient
equivalents, if you prefer) not at startup but every time the device is
activated. The gsettings key hotplug-command in the
Using Precise, Ubuntu session. I experience fuzzy fonts in the panel when using
Radiance or any other theme that has font shadows. A similar issue seems to be
present also in the unity-2d panel, #977080
The same workaround mentioned in that bug-report - namely disabling
text-shadows in the
*** This bug is a duplicate of bug 977080 ***
https://bugs.launchpad.net/bugs/977080
** This bug has been marked a duplicate of bug 977080
Wrong colours in panel when dash opened + coloured pixels around panel text
when using Radiance theme
--
You received this bug notification because
*** This bug is a duplicate of bug 977080 ***
https://bugs.launchpad.net/bugs/977080
** This bug is no longer a duplicate of bug 986865
Panel has buggy fonts while using Radiance on Unity 2d
** This bug has been marked a duplicate of bug 977080
Wrong colours in panel when dash opened +
** Also affects: gnome-panel
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/774581
Title:
Gnome Panel shows in fullscreen mode
To manage notifications
I experience this bug in precise, but not only with vlc but also with totem or
mplayer, so it is obviously not a vlc bug.
It is present in unity and gnome classic, but only under compiz. So using
gnome-panel with metacity is a workaround (alt+F2 metacity --replace)
--
You received this bug
Sorry I have not been clear enough:
The binary virtualbox-fuse vdfuse works equally well with either
virtualbox-ose or virtualbox (PUEL).
Presently, it requires as dependency the ose package only. Installing it
forces uninstalling the puel package.
Making it an or dependency of virtualbox- ose
** Also affects: virtualbox
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/674368
Title:
Please include VBoxHDD.h to allow for packaging of vdfuse
To
VBoxHDD.h is no longer included in uptstream virtualbox-ose. As a
consequence, we cannot compile the vdfuse from virtualbox forum anymore.
The package virtualbox-fuse could be an alternative, however it pulls
virtualbox-ose conflicting with virtualbox-puel. PUEL users still need
vdfuse. I would
Public bug reported:
gimp-plugin-registry includes several python plugins which are installed to:
/usr/share/gimp/2.0/scripts
None of them are visible in GIMP. There is no problem with any of the script-fu
plugins.
This affects:
btn4ws.py
contactsheet.py
file-ora.py
cmyk-tiff-2-cmyk-pdf.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939660
Title:
globally-installed GIMP python plugins are not seen
To manage notifications about this bug go to:
** Summary changed:
- globally-installed GIMP python plugins are not seen
+ globally-installed GIMP python plugins are not accessible
** Also affects: gimp
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- gimp-plugin-registry includes several python plugins which are installed to:
- /usr/share/gimp/2.0/scripts
+ gimp python plugins installed to /usr/share/gimp/2.0/scripts cannot be
+ called by gimp.
+
+ For example, gimp-plugin-registry includes several python plugins
Since gnome3, NetworkManager no longer uses GConf but writes on
/etc/NetworkManager/system-connections/
The 'available to all users' workaround has the main problem that then for the
imported accounts this will save passwords to etc in plaintext and no longer in
the encrypted gnome-keyring. If
In my case (WPA enterprise with TTLS) the password is remembered
independently of the available to all users option. The problem is
that since oneiric it is stored in /etc/NetworkManager as plaintext and
not in the keyring.
--
You received this bug notification because you are a member of Ubuntu
to trigger the migration, you can open gconf-editor and set apps/nm-
applet/stamp to 2. This should migrate the network settings (and reset
then stamp to 3 automatically)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I agree that ideally this should be fixed upstream.
Nevertheless this has not happened yet (additionally today I tried to contact
the author but his mail is bouncing...)
On the other hand, the patch by Tim Potter is so extremely simple; it
will not break anything now nor in the future
--
You
It is especific of gnome-panel but not of gnome-classic session. Running
gnome-panel on gnome-shell or unity also has the same problem. In all
cases, running gnome-panel from the terminal displays the Cannot open
display: error whenever the calendar is clicked.
Additionally, I would like to
** Also affects: evolution-data-server
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/885934
Title:
Double clicking on a date in the calendar of the clock
The bug is still present in Ubuntu when MOZ_NO_REMOTE variable is set (i.e.,
when you use multiple profiles).
The workaround #18 does not work anymore on Natty because Preferred
applications are now hardcoded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Apparently the bug is solved now. With Ubuntu's last 2.6.35-25-generic,
the middle button works again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663806
Title:
Touchpad middle button not
** Description changed:
- The middlebutton of the touchpad in a dell precision m6400 laptop
- stopped working after upgrade to maverick. Apparently it is a problem
- with the current 2.6.35-22-generic kernel, since it is working without
- any problem under any of the mainline kernels.
+ The
There is a dirty workaround: delete the default keyring and disable
/usr/bin/gnome-keyring-daemon. This way you disable all keyring
capabilities but your network password is never stored and it is asked
everytime.
Let me add also that using the Available to all users option (which
makes the
Public bug reported:
By default, all passwords used in nm-applet are cached by GNOME keyring.
From Ubuntu 10.10 version of nm-applet, all wireless connections that
are Dynamic WEP or WPAWPA2 Enterprise have an option called Ask
for this password every time. Nevertheless, these network passwords
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686794
Title:
In nm-applet's Edit Connections, WPA Enterprise has an option Ask for this
password every time but it is not respected
--
ubuntu-bugs
** Attachment removed: Gconf.txt
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/686794/+attachment/1759148/+files/Gconf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment removed: WifiSyslog.txt
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/686794/+attachment/1759153/+files/WifiSyslog.txt
** Attachment removed: IpAddr.txt
I am just confirming that today's update to 2.6.35-23-generic kernel
still has the same problem, and that the equivalent mainline kernel
(package called 2.6.35-02063509) does work. So it seems that running the
mainline kernels is another workaround.
--
Touchpad middle button not working in Dell
** Also affects: window-picker-applet
Importance: Undecided
Status: New
--
[10.04 Netbook] close button is on left while maximized
https://bugs.launchpad.net/bugs/556686
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It is fix-released in unity only. The inconsistency of having buttons at
the right is still present in window-picker-applet (and note that bug
title says 10.04 not 10.10). window-picker-applet is the default in
10.04. Also, it is still useful to many netbook users whose hardware
does not meet the
h3, it seems that you have a different issue. If you read the bug
description it says that kills reader device just means that it stops
being powered and it is not repowered until next reboot. Apparently,
what you experience is a permanent break, so it is something unrelated
to this bug report.
It is a dell precision m6400 (not inspiron, excuse the lapsus). Apparently, the
touchpad is the same in m6500 (they call it trackpad).
Left-right click is a possible workaround, also the top-right tap with the
mouse clicks option in mouse preferences.
** Summary changed:
- Touchpad middle
I confirm that the middle button is working with the last
2.6.32-25-generic kernel of lucid-security, put on the maverick
installation. It is also working with the mainline kernels. It seems to
be specific issue of the maverick kernel.
--
touchpad middle button not working
** Tags added: apport-collected
** Description changed:
The middlebutton of the touchpad in a dell inspiron m6400 laptop stopped
working after upgrade to maverick. Apparently it is a problem with the
current 2.6.35-22-generic kernel, since it is working without any
problem under any of
That previous apport-collect was for the mainline kernel, where
everything works
Later I will repeat the apport-collect for the Ubuntu kernel, where
middlebutton does not work (all the other functions of the touchpad
work)
** Description changed:
The middlebutton of the touchpad in a dell
apport information
** Attachment added: AcpiTables.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711687/+files/AcpiTables.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: AlsaDevices.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711688/+files/AlsaDevices.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: BootDmesg.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711689/+files/BootDmesg.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711690/+files/Card0.Amixer.values.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711691/+files/Card0.Codecs.codec.0.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711692/+files/CurrentDmesg.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: IwConfig.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711693/+files/IwConfig.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711694/+files/Lspci.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711695/+files/Lsusb.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: PciMultimedia.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711696/+files/PciMultimedia.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711697/+files/ProcCpuinfo.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711698/+files/ProcInterrupts.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711699/+files/ProcModules.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
apport information
** Attachment added: RfKill.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711700/+files/RfKill.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711701/+files/UdevDb.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs, which
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711702/+files/UdevLog.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs,
apport information
** Attachment added: WifiSyslog.txt
https://bugs.edge.launchpad.net/bugs/663806/+attachment/1711703/+files/WifiSyslog.txt
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Public bug reported:
The middlebutton of the touchpad in a dell inspiron m6400 laptop stopped
working after upgrade to maverick. Apparently it is a problem with the
current 2.6.35-22-generic kernel, since it is working without any
problem under any of the mainline kernels.
ProblemType: Bug
** Also affects: linux
Importance: Undecided
Status: New
--
touchpad middle button not working
https://bugs.launchpad.net/bugs/663806
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
No, I do not use lvm. I insist in the fact that it was a problem
reproducible in 2.6.31-16 kernel only. grub2 has not given me any
problem with any other kernel.
--
package linux-image failed to install : post-installation script returned error
exit status 137. /usr/sbin/update-grub killed with
Jouni, the problem is with internal readers, which cannot be reconnected
without disassembling the computer.
Also, the description says Drive worked fine until last couple of weeks: do
you mean that this has been a regression in a Karmic update? This is not my
case: since the release of the
I cannot see a regression here: In up-to-date Jaunty (supported updates,
at least), the safely remove option that I see in desktop and nautilus
sidebar is actually called Unmount and it does the same as Unmount
does in Karmic: it unmounts the filesystem.
Unmounting the filesystem does not prevent
I am also experiencing this bug in Karmic with updated thunderbird and firefox.
I discovered that the problem is that I am running firefox with --no-remote
option. It seems that this enables the environment variable MOZ_NO_REMOTE,
which affects thunderbird also. Running thunderbird with env -u
After rebooting to the 2.6.31-15 kernel, I was able to update-grub and
apply the update. Now with kernel -17 everything works also. So it seems
linked to the -16 kernel only, for some reason.
--
package linux-image failed to install : post-installation script returned error
exit status 137.
Here is the result of
sudo strace -f -tt grub-probe -v --target=device / 21 | tee grub-
probe.strace.log
** Attachment added: grub-probe.strace.log
http://launchpadlibrarian.net/37680459/grub-probe.strace.log
--
package linux-image failed to install : post-installation script returned
** Attachment added: lshw.log
http://launchpadlibrarian.net/37683415/lshw.log
--
package linux-image failed to install : post-installation script returned error
exit status 137. /usr/sbin/update-grub killed with SIGKILL
https://bugs.launchpad.net/bugs/504173
You received this bug
I have checked that if I manually run as root update-grub or grub-
mkconfig (with any output file), they get killed too before any output.
Reinstalling grub-pc or grub-common does not change anything.
--
package linux-image failed to install : post-installation script returned error
exit status
This is the result. It seems that SIGKILL occurs after grub-probe.
** Attachment added: log of grub-mkconfig
http://launchpadlibrarian.net/37650311/update-grub.log
--
package linux-image failed to install : post-installation script returned error
exit status 137. /usr/sbin/update-grub
grub-probe -v is killed too, and gives this output:
sudo grub-probe -v --target=device /
grub-probe: info: the size of hd0 is 976773168
grub-probe: info: the size of hd0 is 976773168
grub-probe: info: the size of hd0 is 976773168
Killed
Additionally, I applied this update and run these commands
I did not deliberately kill anything, just update with update manager as
usual.
It is not yet solved: Every time I install a new package with synaptic,
it tries again to install that linux-image and obtain the same error.
--
package linux-image-2.6.31-17-generic 2.6.31-17.54 failed to
Public bug reported:
In Karmic, when updating linux-image 2.6.31-17.54 with Update Manager as
usual
ProblemType: Package
Architecture: amd64
Date: Thu Jan 7 10:08:41 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit
status 137
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/37535222/AptOrdering.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37535223/Dependencies.txt
** Attachment added: Dmesg.txt
http://launchpadlibrarian.net/37535224/Dmesg.txt
** Attachment
91 matches
Mail list logo
