Upgrading the BIOS to version A14 solved the problem for me: I still see
psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
but no erratic movement.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: referencer
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267786
Title:
Referencer hangs on Ubuntu 13.10: gtk thread related changes?
To
** Changed in: referencer
Milestone: None = 1.2.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267786
Title:
Referencer hangs on Ubuntu 13.10: gtk thread related changes?
To manage
** Changed in: referencer
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267786
Title:
Referencer hangs on Ubuntu 13.10: gtk thread related changes?
To
** Changed in: referencer (Ubuntu)
Status: New = Fix Committed
** Changed in: referencer (Ubuntu)
Assignee: (unassigned) = Mads Chr. Olesen (shiyee)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Do you have any BibTex entry that causes a crash?
** Changed in: referencer (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/279066
Title:
Referencer
** Changed in: referencer (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1256567
Title:
gtk deadlocks in referencer
To manage notifications about this bug go
** Changed in: referencer (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262820
Title:
Hangs when adding a document
To manage notifications about this bug
Public bug reported:
Pretty much any interaction involving dialogs, even opening the about dialog
will cause Referencer to hang.
The backtrace looks something like:
#0 __lll_lock_wait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135
#1 0x74144192 in _L_lock_1142 ()
For my own notes: There is a new Gnome3 thumbnailer described at
http://askubuntu.com/questions/199110/how-can-i-instruct-nautilus-to-
pre-generate-thumbnails/201997#201997
** Also affects: referencer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
*** This bug is a duplicate of bug 1267786 ***
https://bugs.launchpad.net/bugs/1267786
** This bug has been marked a duplicate of bug 1267786
Referencer hangs on Ubuntu 13.10: gtk thread related changes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 1267786 ***
https://bugs.launchpad.net/bugs/1267786
** This bug has been marked a duplicate of bug 1267786
Referencer hangs on Ubuntu 13.10: gtk thread related changes?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have not had problems in Ubuntu 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781653
Title:
Mouse is sometimes grabbed, making only keyboard interaction possible
To manage notifications
I have now figured out that the ISACTIVE:true in .xsession-errors
comes from the Nagios Checker firefox plugin, when focusing/unfocusing
the main area of Firefox. I have disabled that plugin and will try to
see if that removes the issue.
To clarify: I suspect there is a bug somewhere in Unity,
Public bug reported:
Binary package hint: unity
Sometimes (unsure of what triggers the bug) the mouse is grabbed by an
application (e.g. Firefox). Then the mouse can only be used to interact
with that single application, but keyboard interaction still works with
that and other apps. When closing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/781653
Title:
Mouse is sometimes grabbed, making only keyboard interaction possible
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 625793 ***
https://bugs.launchpad.net/bugs/625793
Public bug reported:
Binary package hint: gnome-settings-daemon
After upgrade to maverick gnome-settings-daemon uses 100% cpu.
Seems to be related to having multiple keyboard layouts (Danish QWERTY and
*** This bug is a duplicate of bug 625793 ***
https://bugs.launchpad.net/bugs/625793
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/658342/+attachment/1684561/+files/Dependencies.txt
** This bug has been marked a duplicate of bug 625793
Regression: Multiple
Just got a crash:
** (multiadm:18720): CRITICAL **: file gkr-operation.c: line 350
(gkr_operation_request): should not be reached
**
ERROR:gkr-operation.c:392:gkr_operation_block: code should not be reached
Aborted
** Also affects: libgnome-keyring (Ubuntu)
Importance: Undecided
Sorry to people who got subscribed: I wanted to document in MultiADM
that this is related to https://bugs.launchpad.net/ubuntu/+source
/libgnome-keyring/+bug/554077 but obviously failed...
--
multiadm triggers assert in gnome-keyring code
https://bugs.launchpad.net/bugs/613335
You received this
Well, compiz actually tries to prevent this configuration from occuring.
To get a faulty configuration one needs to configure compiz and then
hot-plug the monitor.
The bug is about the limit existing.
You are very welcome to close it as unsupported or similar; I fully realize
that fixing it is a
Public bug reported:
Binary package hint: compiz
I have a nVidia twin-view setup with 2 screens, 1900x1200 and 1680x1050.
I would like to use 12 horizontal virtual desktops. This is currently
not possible.
I have dug a bit into the code (compiz and Xorg), and it seems the
underlying issue is
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38709873/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38709874/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38709875/Dependencies.txt
**
I'm unable to find an authoritative source for this, but purge is not meant to
delete files in users' home dirs.
The reference to configuration files is files stored under /etc, which are
removed when you use purge.
See http://ubuntuforums.org/archive/index.php/t-870311.html
--
Empathy
*** This bug is a duplicate of bug 318265 ***
https://bugs.launchpad.net/bugs/318265
** This bug has been marked a duplicate of bug 318265
Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long
while these codes can be up to 8 digits long
--
nm-applet puk entry allows
As a work-around you can use the SIM card in a mobile phone enter the
PUK-code there, and set a new PIN-code, then use the SIM card without
problems.
--
Network-Manager-Applet asks for PUK and PIN of only up to 4 digits long while
these codes can be up to 8 digits long
** Bug watch added: GNOME Bug Tracker #582435
http://bugzilla.gnome.org/show_bug.cgi?id=582435
** Also affects: network-manager-applet via
http://bugzilla.gnome.org/show_bug.cgi?id=582435
Importance: Unknown
Status: Unknown
--
Network-Manager-Applet asks for PUK and PIN of only
The packages from Saïvann Carignan also solves the problem for me!
--
Tray icon plugin works erratically
https://bugs.launchpad.net/bugs/109312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Initial observations:
First start of evolution after installing ppa packages failed, as in the sync
was taking forever (this also happened before, so I'm not sure its a
regression), so I killed all evolution processes
Second start, sync seems faster than usual.
I will continue testing in the
I fail to understand your argumentation. If the supposed fix (large-
memory) is in Lilo, how can this be a kernel problem?
add a check to lilo that will tell the user that their initrd.img is
over a certain size and that they might want to add the large-memory
option to lilo.conf. This
understanding is that this would just
make lilo behave as if large-memory was specified, in many more cases,
potentially avoiding this gray area.
Thank you very much for taking the time to respond :-)
--
Mads Chr. Olesen [EMAIL PROTECTED]
shiyee.dk
--
lilo needs to warn if initrd is too large
https
Oh bugger. I tried emailing John Coffman, the author of LILO, to get his
take on this (the previous comment), but the mail bounced.
It pretty much sums up my _suspicions_:
LILO has a heuristic to determine when the large-memory option is needed, but
it underestimates, leading to this edge case.
Could you provide the size of the initrd image, gunzipped?
--
lilo needs to warn if initrd is too large
https://bugs.launchpad.net/bugs/260059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hmm, the issue doesn't seem as straightforward after all.
In lilo there is already a check for a too large initrd (boot.c, search
for FLAG_TOOBIG). I wonder why it wasn't triggered.
Could you attach your lilo.conf? And, if possible, the output of running
lilo with a couple of -v flags (and
If access to an affected server is required for testing, please ping me
and I can probably set one up.
--
Cannot authenticate to some webdav shares
https://bugs.launchpad.net/bugs/251822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that the package from -proposed fixes this problem.
--
Cannot authenticate to some webdav shares
https://bugs.launchpad.net/bugs/251822
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This issue has now been resolved in libsoup trunk.
** Tags added: patch
** Attachment added: This is the patch applied to libsoup trunk.
http://launchpadlibrarian.net/16345372/soup-auth-digest-default-to-md5-patch-r1113-r1114-from-svn.patch
--
Cannot authenticate to some webdav shares
** Attachment added: Make libsoup default to MD5 as digest algorithm (as
stated by the RFC)
http://launchpadlibrarian.net/16301544/libsoup-digest-algorithm-default.patch
** Bug watch added: GNOME Bug Tracker #544681
http://bugzilla.gnome.org/show_bug.cgi?id=544681
** Also affects: gvfs
Public bug reported:
Binary package hint: gvfs
When trying to mount some webdav shares (which worked fine under gnomevfs),
gvfs is unable to authenticate.
This is due to the server not returning an algorithm to use, and libsoup (which
gvfs uses for webdav) interprets this wrongly. The RFC is
Public bug reported:
Binary package hint: gvfs-backends
The gvfs dav backend does not handle redirects. This is fixed upstream, and has
a very small patch.
Would be really nice to have this in, before the release.
** Affects: gvfs
Importance: Unknown
Status: Unknown
** Affects:
** Attachment added: screenshot of problem
http://launchpadlibrarian.net/13784525/Sk%C3%A6rmbillede-nautilus.png
--
gvfs dav backend does not handle redirects [PATCH]
https://bugs.launchpad.net/bugs/220516
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: patch from upstream at
http://svn.gnome.org/viewvc/gvfs/branches/gnome-2-22/daemon/gvfsbackenddav.c?view=patchr1=1725r2=1741pathrev=1741;
http://launchpadlibrarian.net/13785307/94_from_svn_fix_dav_redirect_issue.patch
** Bug watch added: GNOME Bug Tracker #528218
Hmm, sorry for the noise - my bug seems to be unrelated, but related to
specifying a username in the URI and there after being redirected.
** Changed in: gvfs (Ubuntu)
Status: New = Invalid
--
gvfs dav backend does not handle redirects [PATCH]
https://bugs.launchpad.net/bugs/220516
You
This patch is now in libvirt trunk.
--
Does not support routed virtual network
https://bugs.launchpad.net/bugs/190904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: Updated patch, see discussion on libvirt mail list
http://launchpadlibrarian.net/12554211/routed-virtual-net.0.4.0.patch
--
Does not support routed virtual network
https://bugs.launchpad.net/bugs/190904
You received this bug notification because you are a member of
** Attachment added: Updated patch
http://launchpadlibrarian.net/12519061/routed-virtual-net.patch
--
Does not support routed virtual network
https://bugs.launchpad.net/bugs/190904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Please see the attached patch, which allows the use of a
route dev=ethX / stanza (dev is optional), much like the forward / stanza.
Comments welcome :-)
** Attachment added: Allow use of route dev=ethX /
http://launchpadlibrarian.net/12356895/routed-virtual-net.patch
--
Does not supported
Public bug reported:
With libvirt0 version 0.4.0-2ubuntu4, i get the following upon
/etc/init.d/libvirt-bin start:
Feb 13 18:23:04 lukas kernel: [79696.733582] vnet0: Dropping NETIF_F_UFO since
no NETIF_F_HW_CSUM feature.
Feb 13 18:23:04 lukas kernel: [79696.731640] vnet0: starting userspace
AHA!
Creating the directory /var/lib/libvirt/ seems to be the solution
--
[hardy] dnsmasq fails to start the dhcp server
https://bugs.launchpad.net/bugs/191636
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Public bug reported:
If iptables is not installed, /etc/init.d/libvirtd start gives this error:
libvir: QEMU error : failed to add iptables rule to allow DHCP requests from
'virbr0' : Invalid argument
Failed to autostart network 'default': failed to add iptables rule to allow
DHCP requests from
Have you edited your /etc/apt/sources.list file manually, or only used tools?
The error comes from a line that has an erroneus at the start, e.g.
deb ...
instead of
deb ...
--
E: Type '“deb' is not known on line 44 in source list /etc/apt/sources.lis
https://bugs.launchpad.net/bugs/182918
You
For the moment I'm using the attached script after each re-login, as a
workaround.
** Attachment added: Workaround script
http://launchpadlibrarian.net/9297234/fix-compiz-keybindings.sh
--
Unable to deactivate shortcut key for some general actions
https://bugs.launchpad.net/bugs/139445
You
Public bug reported:
Binary package hint: compizconfig-settings-manager
I'm unable to disable the shortcut keys for the actions found under
General Options - Actions - General, such as:
* Close Window (Alt+f4)
* Maximize (Alt+f10)
* Minimize
* Slow animations
* ...
I have tried both
Public bug reported:
Binary package hint: network-manager
The recent upgrade of network-manager to 0.6.5-0ubuntu11 has broken
network-manager support for me, NetworkManager seems to segfault. Syslog
attached.
** Affects: network-manager (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: Working nm
http://launchpadlibrarian.net/9233999/working-nm.log
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/bugs/138917
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: Segfaulting nm
http://launchpadlibrarian.net/9233998/broken-nm.log
--
network-manager 0.6.5-0ubuntu11 broken
https://bugs.launchpad.net/bugs/138917
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The difference is in the lines:
Sep 11 13:55:46 localhost NetworkManager: info SUP: sending command
'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant2^I'
Sep 11 13:55:46 localhost NetworkManager: info SUP: response was 'FAIL'
(broken)
vs.
Sep 11 17:29:56 localhost NetworkManager: info
Reading the patches that went into 0.6.5-0ubuntu11, its probably
41t_nm_device_wireless_index_ctrl_sockets_by_run_count.patch thats causing the
problems, more specifically the hunk:
@@ -2808,27 +2822,30 @@
wpa_driver = madwifi;
else if (!strcmp (kernel_driver,
Public bug reported:
Binary package hint: nautilus-cd-burner
I'm unable to burn an ISO-file to a disk, using nautilus-cd-burner. The
symptoms is that n-c-b locks up, and consumes more and more memory.
The problem is that n-c-b calls cdrecord as:
cdrecord fs=16m dev=0,1,0 -eject -dao
It seems I had a locally installed version of n-c-b.
The one from the Ubuntu package works flawlessly.
This bug can be closed, very sorry for the disturbance..
** Changed in: nautilus-cd-burner (Ubuntu)
Status: Incomplete = Invalid
--
[Gutsy] Cannot burn, n-c-b sends wrong device
service-discovery-applet is an Avahi service browser for the gnome
panel. You add it to your gnome panel, click the icon choose VNC Remote
Access (given that you have a vnc service advertised at your LAN), and
click a service to connect to it.
--
[Gutsy] xvncviewer support broken by new version
Public bug reported:
Binary package hint: liferea
The Ctrl+N hotkey is bound to both New Folder and Next Unread Item.
** Affects: liferea (Ubuntu)
Importance: Undecided
Status: New
--
Ctrl+N hotkey bound to both New Folder and Next Unread Item
Public bug reported:
Binary package hint: service-discovery-applet
The current version of xvnc4viewer in Gutsy does not support the -xrm
*passwordDialog:true option which the plugin passes to it.
Just removing the parameters works, as the new default is opening a X
password dialog, see attached
** Attachment added: xvnc4viewer-sda.patch
http://launchpadlibrarian.net/8693856/xvnc4viewer-sda.patch
--
[Gutsy] xvncviewer support broken by new version 4.1.1
https://bugs.launchpad.net/bugs/130334
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Still seeing this in gutsy with apt-listchanges version 2.74ubuntu2
Probably apt-listchanges should just depend on mail-transport-agent ?
--
[apport] apt-listchanges crashed with IOError in mail_changes()
https://bugs.launchpad.net/bugs/85031
You received this bug notification because you are a
Attached is the output of
grep tex /var/log/dpkg.log.1
Hope this helps :-)
** Attachment added: grep tex /var/log/dpkg.log.1
http://launchpadlibrarian.net/8289449/tex-dpkg.log
--
package texlive-base-bin 2007-11 failed to install/upgrade: post-installation
script spawns thousands of
, but
if I assume it resembles sarge (tex-common 1.0*), *then* I do not
have
an explanation.
We should really try to get exact version numbers (aptitude log?)
I cannot find any information in /var/log/aptitude* about version
numbers.
--
Mads Chr. Olesen [EMAIL PROTECTED]
shiyee.dk
likely the
reporter is not using aptitude.
Actually I am, but I think I used apt-get for the dist-upgrade :-(
--
Mads Chr. Olesen [EMAIL PROTECTED]
shiyee.dk
--
package texlive-base-bin 2007-11 failed to install/upgrade: post-installation
script spawns thousands of processes
https
removing xmltex and jadetex seems to solve the problem :-)
Thanks! - I guess this bug can be closed
--
package texlive-base-bin 2007-11 failed to install/upgrade: post-installation
script spawns thousands of processes
https://bugs.launchpad.net/bugs/122863
You received this bug notification
In my testing, it does NOT work.
When setting config.use_system_prefs the settings you listed become locked,
and the firefox network dialog becomes grayed out.
The settings from gconf is however not used, in about:config e.g. type is 0 (no
proxy) and the various host fields are blank.
I have
Yes, I also tested whether it works, admittedly only by setting the
proxy and seeing that i'm still able to connect which should not be
possible if it used the non-accessible proxy server.
--
firefox(-gnome-support) should get proxy from gconf
https://bugs.launchpad.net/bugs/23369
You received
*** This bug is a duplicate of bug 69049 ***
https://bugs.launchpad.net/bugs/69049
** This bug has been marked a duplicate of bug 69049
Several tool hotkeys do not work
--
keyboard shortcut for drawing an ellipse is unusable
https://bugs.launchpad.net/bugs/95055
You received this bug
** Bug watch added: GNOME Bug Tracker #439935
http://bugzilla.gnome.org/show_bug.cgi?id=439935
** Also affects: dia (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=439935
Importance: Unknown
Status: Unknown
--
Dia: automatic file name extension for export
Public bug reported:
Binary package hint: beagle
As described by Joe Shaw in
http://thomas.apestaart.org/log/?p=482#comment-2699 beagle will fall-
back to continously indexing a user's files, if it fails to inotfy watch
all directories for changes. The described solution is increasing
This is possibly also the cause for bug #77106
--
max inotify user watches in the kernel should be increased for beagle indexing
to be optimal
https://bugs.launchpad.net/bugs/115801
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
could you try to run gabble in debug mode?
1. Start GABBLE_DEBUG=all telepathy-gabble in a terminal
2. Start gossip as usual
3. paste the output from the terminal in this bug report
--
Cannot connect to Jabber server
https://bugs.launchpad.net/bugs/112601
You received this bug notification
The problem is the lines:
** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The certificate
can not be trusted.
** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The certificate
has expired.
** (telepathy-gabble:17804): DEBUG: connection_ssl_cb: called: The server
I just noticed that you seem to be registering with the server?
** (telepathy-gabble:11973): DEBUG: parse_parameters: accepted value 1 for
param register
Try to just log in normally.
--
Cannot connect to Jabber server
https://bugs.launchpad.net/bugs/112601
You received this bug notification
Login ID: [EMAIL PROTECTED]
Server: murrayc.com
If you use SSL, port should be 5223, 5222 otherwise.
--
Can't connect to Jabber accounts
https://launchpad.net/bugs/94385
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Alex: The interaction with gnome-session is that gnome-session sets the env.
var. according to gconf, and this setting is then inherited by all other apps
in the session, see pstree:
│ └─gnome-session─┬─Xgl
│ ├─beagle-search───2*[{beagle-search}]
I'm seeing an issue, that if the proxy is set (manual proxy configuration) on
bootup, changes to the proxy-settings are ignored.
If the proxy is set to Direct internet connection on bootup spawned terminals
obey the settings set at the time they are spawned (as expected).
Looking at the code for
Investigating further, I think the bug is in gnome-session which have
had some changes to set the http_proxy environment variable according to
the gconf settings - this however interferes with gnome-terminal's idea
that if the environment variable is set it should obey this.
The root of the
Attached patch is preliminary fix (disables proxy env. var. setting).
Also filed in gnome bugzilla, bug #398140.
** Attachment added: Disable proxy setting in gnome-session
http://librarian.launchpad.net/5786647/no-setting-proxy-env.patch
--
http_proxy defined incorrectly
I can also confirm bug and that the fix works.
--
boot fails: does not detect hda any more (port conflict?)
https://launchpad.net/bugs/76872
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
84 matches
Mail list logo
