[Bug 1871728] Re: geoclue agent process persists after user logout
As a workaround, I changed /etc/systemd/logind.conf by putting: KillUserProcesses=yes There might be sideeffects though, like the 'screen' command not surviving the logout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871728] Re: geoclue agent process persists after user logout
On UbuntuMATE 20.04, after logging out, the login session remains in state 'closing', blocked by the /usr/libexec/geoclue-2.0/demos/agent process. The loginctl command shows accumulating sessions. loginctl session-status shows: c2 - ebp-admin (1000) Since: Tue 2021-03-23 03:51:12 PDT; 3min 20s ago Leader: 1149 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: mate State: closing Unit: session-c2.scope └─1547 /usr/libexec/geoclue-2.0/demos/agent Mar 23 03:51:12 ubuntu systemd[1]: Started Session c2 of user ebp-admin. Mar 23 03:51:14 ubuntu mate-session[1175]: WARNING: Unable to find provider '' of required component 'dock' Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The SSH agent was already initialized Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The Secret Service was already initialized Mar 23 03:51:16 ubuntu gnome-keyring-daemon[1172]: The PKCS#11 component was already initialized Mar 23 03:51:28 ubuntu pkexec[1888]: pam_unix(polkit-1:session): session opened for user root by (uid=1000) Mar 23 03:51:28 ubuntu pkexec[1888]: ebp-admin: Executing command [USER=root] [TTY=unknown] [CWD=/home/ebp-admin] [COMMAND=/usr/lib/updat> Mar 23 03:52:17 ubuntu lightdm[1149]: pam_unix(lightdm:session): session closed for user ebp-admin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871728] Re: geoclue agent process persists after user logout
Same behavior on Ubuntu derivatives Linux Mint 20.1 MATE and Cinnamon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871728 Title: geoclue agent process persists after user logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1871728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777428] [NEW] UpdateManager does not work behind proxy in many cases
Public bug reported: update-manager does not work behind a proxy in many cases. reason: update-manager calls method init_proxy() in UpdateManager/Core/utils.py. This method does not implement what is described in its documentation string: 1. the implementation does not check the http_proxy environment variable 2. it tries to read the file /root/.synaptic/synaptic.conf, but due to the access rights drwx-- on the '/root' directory, it can't read the file, unless the user is exactly 'root', but that is rightly completely discouraged by Ubuntu. The only option that works is the addition of Acquire::http::Proxy to some config file in /etc/apt/apt.conf.d It means that update-manager does not work when the user has added proxy settings in its Preferences. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3-update-manager 1:18.04.11.2 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 18 13:37:42 2018 GsettingsChanges: b'com.ubuntu.update-manager' b'window-height' b'671' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'898' b'com.ubuntu.update-manager' b'launch-time' b'int64 1529319882' InstallationDate: Installed on 2018-05-15 (34 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777428 Title: UpdateManager does not work behind proxy in many cases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1777428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129949] Re: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com
Please restore the package on archive.ubuntu.com ** Package changed: grail (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129949 Title: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1129949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 942106] Re: software raid doesn't assemble before mount on boot
The patch of https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/942106/comments/5 does not work in following case: - Ubuntu 12.04 - partitionable RAID-1 on two complete disks sda and sdb, giving array md0. Root partition is md0p1, swap partition is md0p2. - One disk physically removed before boot. - boot degraded arrays is requested The system reports Mount failed, /dev/disk/my-uuid/uniqueid busy. This /dev/disk/my-uuid/uniqueid points to /dev/sda1. Solution: add a second wait_for_udev at the end of the local-premount/mdadm script. This results in the script: . /scripts/mdadm-functions . /scripts/functions wait_for_udev degraded_arrays || exit 0 mountroot_fail || panic Dropping to a shell. wait_for_udev - Hypothetical explanation: mountroot_fail finds a degraded RAID-1 array and starts it with one disk, creating device /dev/md0. The function ends. Next, the 'local' script tries to mount the root partition, but udev did not yet have time to detect the partitions and create the corresponding devices md0p1 and md0p1, and change the links in /dev/disk/by-uuid to these detected partitions. The links in /dev/disk/by-uuid still point to /dev/sda[12], which are locked by mdadm for md0. The added wait_for_udev lets udev find the partitions md0p1 and md0p2 and change the links in /dev/disk/by-uuid before trying to mount the root partition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/942106 Title: software raid doesn't assemble before mount on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/942106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129949] [NEW] corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com
Public bug reported: The libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on the main Ubuntu mirror archve.ubuntu.com is corrupt. This is also the case on several other mirrors. ** Affects: grail (Ubuntu) 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/1129949 Title: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grail/+bug/1129949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129949] Re: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com
** Attachment added: Valid package from de.archive.ubuntu.com https://bugs.launchpad.net/ubuntu/+source/grail/+bug/1129949/+attachment/3536209/+files/libgrail5_3.0.6-0ubuntu0.12.04.01_i386%281%29.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129949 Title: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grail/+bug/1129949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1129949] Re: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com
** Attachment added: corrupt package https://bugs.launchpad.net/ubuntu/+source/grail/+bug/1129949/+attachment/3536208/+files/libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1129949 Title: corrupt package libgrail5_3.0.6-0ubuntu0.12.04.01_i386.deb on archive.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grail/+bug/1129949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096816] [NEW] regression: libesd0 fails to handle case where sound daemon is not running
Public bug reported: In version 0.2.41: In esdlib.c : function connect_timeout(): If no sound daemon (esd or pulseaudio with esound-compat) is running, the function will not return -1 (meaning that the connection failed). The reason: connect() on a non-blocking socket always returns EINPROGRESS even if the destination is not present. The subsequent poll() call returns in revents: POLLIN|POLLOUT|POLLERR|POLLHUP but the code only tests on POLLIN and POLLOUT and then decides in error that the connection was succesfull and the function returns 0. This causes the library to not read the ~/.esd.conf . It then fails to honor the autospawn entry in that config file. This problem becomes apparent when runnng graphical sessions with simple window managers such as fvwm2. This window manager does not start pulseaudio automatically. This problem was not present in version 0.2.38 of the library (in Ubuntu Hardy). ** Affects: esound (Ubuntu) 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/1096816 Title: regression: libesd0 fails to handle case where sound daemon is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/esound/+bug/1096816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 822619] [NEW] With automatic logon first keypress switches key repetition back on
Public bug reported: Package: gdm 2.30.2.is.2.30.0-0ubuntu5.2+langfixes~lucid1 Ubuntu 10.04 LTS (up to date) We have following situation: - GDM configured with timed automatic login - FVWM session with automatic execution of the 'xset r off' command during startup to switch off keyboard repeat. We have proof that the xset command is executed properly because 'xset q' commands afterwards show that the keyboard repeat really is switched off. Pressing any keyboard key automagically switches the keyboard repetition back on. This phenomenon also happens with the 'xterm' session. In that case switching off and verifying the keyboard repetition has to be done via a console (Shift+Alt+F1). Pressing a key before the automatic logon timer expires avoids the phenomenon. This phenomenon was not present in Ubuntu 8.04 LTS. This phenomenon causes problems for using this Ubuntu version as base for Kiosk applications ** Affects: gdm (Ubuntu) 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/822619 Title: With automatic logon first keypress switches key repetition back on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/822619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575026] Re: xfstt crashes in lucid lynx
tThe buffer overflow reported by the fortify checks in sprintf is caused by the fact that the sprintf call on line 449 in xfstt.cc does not account for the terminating \0. The size of the target buffer fn.panose is exactly 20 bytes, and the code tries to write 20 chars + 1 terminating \0 into it. I attached a patch fixing this problem. Note that the source of xfstt in Debian sid (xfstt version 1.7-7) has the same problem. ** Patch added: patch correcting buffer overflow in sprintf call http://launchpadlibrarian.net/47873908/sprintf_buferoverflow.patch -- xfstt crashes in lucid lynx https://bugs.launchpad.net/bugs/575026 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 575026] [NEW] xfstt crashes in lucid lynx
Public bug reported: Binary package hint: xfstt xfstt crashes when requesting its fonts list with fslsfonts. fslsfonts -server unix/:7101 returns FSIO: fatal IO error 32 (Broken pipe) on font server unix/:7101 after 1 requests (0 known processed) with 0 events remaining. The connection was probably broken by a server shutdown. When running xfstt in foreground and calling fslsfonts in another terminal we get: # xfstt *** buffer overflow detected ***: xfstt terminated === Backtrace: = /lib/tls/i686/cmov/libc.so.6(__fortify_fail+0x50)[0xb89350] /lib/tls/i686/cmov/libc.so.6(+0xe128a)[0xb8828a] /lib/tls/i686/cmov/libc.so.6(+0xe09c8)[0xb879c8] /lib/tls/i686/cmov/libc.so.6(_IO_default_xsputn+0x9e)[0xb10afe] /lib/tls/i686/cmov/libc.so.6(_IO_vfprintf+0xe24)[0xae4a34] /lib/tls/i686/cmov/libc.so.6(__vsprintf_chk+0xad)[0xb87a7d] /lib/tls/i686/cmov/libc.so.6(__sprintf_chk+0x2d)[0xb879bd] xfstt[0x804c657] === Memory map: 0015e000-0015f000 r-xp 00:00 0 [vdso] 00382000-003a6000 r-xp 08:01 69004 /lib/tls/i686/cmov/libm-2.11.1.so 003a6000-003a7000 r--p 00023000 08:01 69004 /lib/tls/i686/cmov/libm-2.11.1.so 003a7000-003a8000 rw-p 00024000 08:01 69004 /lib/tls/i686/cmov/libm-2.11.1.so 00713000-007fc000 r-xp 08:01 3341 /usr/lib/libstdc++.so.6.0.13 007fc000-007fd000 ---p 000e9000 08:01 3341 /usr/lib/libstdc++.so.6.0.13 007fd000-00801000 r--p 000e9000 08:01 3341 /usr/lib/libstdc++.so.6.0.13 00801000-00802000 rw-p 000ed000 08:01 3341 /usr/lib/libstdc++.so.6.0.13 00802000-00809000 rw-p 00:00 0 00a41000-00a5c000 r-xp 08:01 18487 /lib/ld-2.11.1.so 00a5c000-00a5d000 r--p 0001a000 08:01 18487 /lib/ld-2.11.1.so 00a5d000-00a5e000 rw-p 0001b000 08:01 18487 /lib/ld-2.11.1.so 00aa7000-00bfa000 r-xp 08:01 68966 /lib/tls/i686/cmov/libc-2.11.1.so 00bfa000-00bfb000 ---p 00153000 08:01 68966 /lib/tls/i686/cmov/libc-2.11.1.so 00bfb000-00bfd000 r--p 00153000 08:01 68966 /lib/tls/i686/cmov/libc-2.11.1.so 00bfd000-00bfe000 rw-p 00155000 08:01 68966 /lib/tls/i686/cmov/libc-2.11.1.so 00bfe000-00c01000 rw-p 00:00 0 00e4d000-00e6a000 r-xp 08:01 20481 /lib/libgcc_s.so.1 00e6a000-00e6b000 r--p 0001c000 08:01 20481 /lib/libgcc_s.so.1 00e6b000-00e6c000 rw-p 0001d000 08:01 20481 /lib/libgcc_s.so.1 08048000-0806 r-xp 08:01 63034 /usr/bin/xfstt 0806-08061000 r--p 00017000 08:01 63034 /usr/bin/xfstt 08061000-08062000 rw-p 00018000 08:01 63034 /usr/bin/xfstt 08062000-0806d000 rw-p 00:00 0 09186000-091a7000 rw-p 00:00 0 [heap] b71fc000-b767e000 rw-p 00:00 0 b767e000-b7682000 r--s 08:01 65417 /var/cache/xfstt/ttname.dir b7682000-b7683000 r--s 08:01 65376 /var/cache/xfstt/ttinfo.dir b7683000-b76c2000 r--p 08:01 1738 /usr/lib/locale/en_US.utf8/LC_CTYPE b76c2000-b76c3000 r--p 08:01 15159 /usr/lib/locale/en_US.utf8/LC_NUMERIC b76c3000-b76c4000 r--p 08:01 9427 /usr/lib/locale/en_US.utf8/LC_TIME b76c4000-b77e2000 r--p 08:01 2410 /usr/lib/locale/en_US.utf8/LC_COLLATE b77e2000-b77e4000 rw-p 00:00 0 b77e4000-b77e5000 r--p 08:01 39615 /usr/lib/locale/en_US.utf8/LC_MONETARY b77e5000-b77e6000 r--p 08:01 39616 /usr/lib/locale/en_US.utf8/LC_MESSAGES/SYS_LC_MESSAGES b77e6000-b77e7000 r--p 08:01 15095 /usr/lib/locale/en_US.utf8/LC_PAPER b77e7000-b77e8000 r--p 08:01 15158 /usr/lib/locale/en_US.utf8/LC_NAME b77e8000-b77e9000 r--p 08:01 42265 /usr/lib/locale/en_US.utf8/LC_ADDRESS b77e9000-b77ea000 r--p 08:01 48946 /usr/lib/locale/en_US.utf8/LC_TELEPHONE b77ea000-b77eb000 r--p 08:01 15091 /usr/lib/locale/en_US.utf8/LC_MEASUREMENT b77eb000-b77f2000 r--s 08:01 68543 /usr/lib/gconv/gconv-modules.cache b77f2000-b77f3000 r--p 08:01 48959 /usr/lib/locale/en_US.utf8/LC_IDENTIFICATION b77f3000-b77f5000 rw-p 00:00 0 bfb9d000-bfbb2000 rw-p 00:00 0 [stack] ** Affects: xfstt (Ubuntu) Importance: Undecided Status: New -- xfstt crashes in lucid lynx https://bugs.launchpad.net/bugs/575026 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574409] [NEW] font not available as X font after installation
Public bug reported: Binary package hint: ttf-dejavu In 8.04LTS the dejavu truetype font becomes avalailable as X font: it shows up in the results of xlsfonts. This means that programs using basic X windows functions (Xlib, Xt or even Motif) can use the fonts. However, in 10.04LTS this is not the case anymore. Why? ** Affects: ttf-dejavu (Ubuntu) Importance: Undecided Status: New -- font not available as X font after installation https://bugs.launchpad.net/bugs/574409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] Re: left mouse button unresponsive when running as VMware server guest
I tried the proposed solution and it seems to solve the problem. -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] Re: left mouse button unresponsive when running as VMware server guest
** Attachment added: dmesg output for lucid live beta 1 after ocurrence of problem http://launchpadlibrarian.net/43330849/dmesg-live-beta1.out -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] Re: left mouse button unresponsive when running as VMware server guest
** Attachment added: Xorg.log of lucid live beta 1 after occurrence of problem http://launchpadlibrarian.net/43330918/Xorg.1.log.live-beta1 -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] Re: left mouse button unresponsive when running as VMware server guest
I installed the beta 1 of Lucid in its virtual machine and updated it on today. I also add the dmesg output and Xorg.log of it. ** Attachment added: dmesg output of lucid installed and updated on 2010/04/07 http://launchpadlibrarian.net/43331159/dmesg.out.20100407 -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] Re: left mouse button unresponsive when running as VMware server guest
** Attachment added: Xorg.log of lucid beta 1 updated on 2010./04/07 http://launchpadlibrarian.net/43331221/Xorg.0.log.20100407 -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545298] [NEW] left mouse button unresponsive when running as VMware server guest
Public bug reported: Binary package hint: xserver-xorg-input-vmmouse Running Ubuntu 10.04 LTS Beta 1 Live CD session as a VMWare Server 2.0.2 quest. The Vmware graphical console runs on Windows XP and is connected to the VMware server over 10MBit Ethernet. The VMware Server host is a Ubuntu 8.04 LTS Intel system. I selected a solid background as desktop background in 10.04 Beta 1. I switched the VMware console to full screen. Then I opened a terminal window and dragged it vigorously around for about 10 secs by clicking and dragging its title bar. After some attempts, when I release the mouse button, the release event is not noticed by the window manager and I can keep dragging around the window (although no mouse button is pressed). The dragging stops when hit the Escape key.However,from then on left mouse button clicks are ignored: I can't click on icons, nor select menus, nor start programs in the top menu bar. Switching back the console from full screen mode to windowed mode and then dragging a window by using the right mouse button and the menu item Move on the title bar and then dragging a little, restores the normal mouse behavior. Apparently I can't use ubuntu-bug because I am behind an authenticating proxy server. ** Affects: xserver-xorg-input-vmmouse (Ubuntu) Importance: Undecided Status: New -- left mouse button unresponsive when running as VMware server guest https://bugs.launchpad.net/bugs/545298 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 372717] [NEW] enh: patch for extra NoCursor option
Public bug reported:
In older versions of Vvnc there was an option to switch off the display of the
mouse cursor. This option was useful when
using Xvnc to provide a view-only image.
This option is not present anymore in the current version of Xvnc.
Here follows a patch that reimplements that option. Feel free to include it in
subsequent versions of Xvnc.
The new option is called 'NoCursor'. The change consists of only 6 lines.
Many thanks.
File vnc4-4.1.1+xorg1.0.2/unix/xc/programs/Xserver/vnc:
--- XserverDesktop.cc.orig 2009-05-06 15:50:03.0 +0200
+++ XserverDesktop.cc 2009-05-05 19:10:07.0 +0200
@@ -72,6 +72,9 @@
rejecting the connection,
10);
+BoolParameter noCursor(NoCursor,
+ Don't put up a cursor, false);
+
static KeyCode KeysymToKeycode(KeySymsPtr keymap, KeySym ks, int* col);
static rdr::U8 reverseBits[] = {
@@ -343,6 +346,9 @@
void XserverDesktop::setCursor(CursorPtr cursor)
{
+ if(noCursor)
+return;
+
try {
int w = cursor-bits-width;
int h = cursor-bits-height;
** Affects: vnc4 (Ubuntu)
Importance: Undecided
Status: New
--
enh: patch for extra NoCursor option
https://bugs.launchpad.net/bugs/372717
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304015] [NEW] implementation for missing 'sample pan' functionality (patch)
Public bug reported: Binary package hint: pulseaudio-esound-compat Our application needs to set the volume of stored samples. (the 'sample pan' functionality). This functionality is not yet implemented in pulseaudio 0.9.10 in 8.04 LTS. We implemented it ourselves and present the resulting patch to ubuntu. Please consider including the patch in the next update of the pulseaudio-esound-compat package if possible. Thanks. Please find the patch in attachment. This patch has been generated against protocol-esound.c of 0.9.10. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- implementation for missing 'sample pan' functionality (patch) https://bugs.launchpad.net/bugs/304015 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 304015] Re: implementation for missing 'sample pan' functionality (patch)
** Attachment added: implementation of 'sample pan' functionality. http://launchpadlibrarian.net/20098857/protocol-esound.c.diff -- implementation for missing 'sample pan' functionality (patch) https://bugs.launchpad.net/bugs/304015 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132400] Re: 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system
Although Sarah Hobbs changed the affected module from linux-restricted- modules-2.6.15 to linux-restricted-modules-2.6.12, I think that was not correct since 2.6.12 is related to Breezy while my bug report is related to Dapper. That is why I set the affected module back to linux- restricted-modules-2.6.15. ** Changed in: linux-restricted-modules-2.6.15 (Ubuntu) Sourcepackagename: linux-restricted-modules-2.6.12 = linux-restricted-modules-2.6.15 -- 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system https://bugs.launchpad.net/bugs/132400 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132400] Re: 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system
Forgot to mention: the problem does NOT occur with Feisty. The generic kernel and the nvidia-glx of Feisty are OK. -- 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system https://bugs.launchpad.net/bugs/132400 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 132400] 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system
Public bug reported: Binary package hint: nvidia-glx OS: Ubuntu 6.06LTS up to date with the current repositories Kernel: 2.6.15-28-686 (SMP) Computer: Fujitsu-Siemens R540 with Dual core Xeon processor Video adapter: Nvidia Quadro NVS 440 This video adapter is only supported by the vesa driver (single screen) and the proprietary nvidia driver (all 4 screens). When using the nvidia-glx 1.0.8776 package of 6.06LTS the GUI locks up after some random time. Ssh connections to the PC still work, but restarting X sometimes makes the PC lock up completely. The GUI lock up becomes more probable after having a OpenGL screen saver active for some times. The var/log/kern.log contains following lines just before the lockup: Aug 13 14:02:12 ubuntu kernel: [17180850.34] irq 185: nobody cared (try booting with the irqpoll option) Aug 13 14:02:12 ubuntu kernel: [17180850.34] [__report_bad_irq+42/160] __report_bad_irq+0x2a/0xa0 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [handle_IRQ_event+61/112] handle_IRQ_event+0x3d/0x70 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [note_interrupt+135/240] note_interrupt+0x87/0xf0 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [__do_IRQ+253/272] __do_IRQ+0xfd/0x110 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [do_IRQ+25/48] do_IRQ+0x19/0x30 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [common_interrupt+26/32] common_interrupt+0x1a/0x20 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [mwait_idle+42/64] mwait_idle+0x2a/0x40 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [cpu_idle+111/192] cpu_idle+0x6f/0xc0 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [start_kernel+415/512] start_kernel+0x19f/0x200 Aug 13 14:02:12 ubuntu kernel: [17180850.34] [unknown_bootoption+0/496] unknown_bootoption+0x0/0x1f0 Aug 13 14:02:12 ubuntu kernel: [17180850.34] handlers: Aug 13 14:02:12 ubuntu kernel: [17180850.34] [pg0+944546240/1069167616] (usb_hcd_irq+0x0/0x70 [usbcore]) Aug 13 14:02:12 ubuntu kernel: [17180850.34] [pg0+953752601/1069167616] (nv_kern_isr+0x0/0x64 [nvidia]) Aug 13 14:02:12 ubuntu kernel: [17180850.34] Disabling IRQ #185 Aug 13 14:02:16 ubuntu kernel: [17180854.276000] NVRM: Xid (000a:00): 8, Channel 0020 Aug 13 14:02:19 ubuntu kernel: [17180857.276000] NVRM: Xid (000a:00): 16, Head Count 11b2 Aug 13 14:02:19 ubuntu kernel: [17180857.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11ac Aug 13 14:02:28 ubuntu kernel: [17180866.276000] NVRM: Xid (000a:00): 16, Head Count 11b3 Aug 13 14:02:28 ubuntu kernel: [17180866.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11ad Aug 13 14:02:36 ubuntu kernel: [17180874.276000] NVRM: Xid (000a:00): 16, Head Count 11b4 Aug 13 14:02:36 ubuntu kernel: [17180874.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11ae Aug 13 14:02:44 ubuntu kernel: [17180882.276000] NVRM: Xid (000a:00): 16, Head Count 11b5 Aug 13 14:02:44 ubuntu kernel: [17180882.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11af Aug 13 14:02:52 ubuntu kernel: [17180890.276000] NVRM: Xid (000a:00): 16, Head Count 11b6 Aug 13 14:02:52 ubuntu kernel: [17180890.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11b0 Aug 13 14:03:00 ubuntu kernel: [17180898.276000] NVRM: Xid (000a:00): 16, Head Count 11b7 Aug 13 14:03:00 ubuntu kernel: [17180898.276000] NVRM: Xid (000a:00): 16, Head 0001 Count 11b1 Aug 13 14:03:08 ubuntu kernel: [17180906.292000] NVRM: Xid (000a:00): 16, Head Count 11b8 Aug 13 14:03:08 ubuntu kernel: [17180906.296000] NVRM: Xid (000a:00): 16, Head 0001 Count 11b2 The nvidia video adapter shares its IRQ with the USB drivers. /proc/interrupts: CPU0 CPU1 0: 18436501 54IO-APIC-edge timer 1: 1 8IO-APIC-edge i8042 8: 65 2IO-APIC-edge rtc 9: 0 0 IO-APIC-level acpi 12: 140225 3IO-APIC-edge i8042 14:1271342 1IO-APIC-edge ide0 90: 75913 1 IO-APIC-level libata, uhci_hcd:usb2 98:1393683 1 IO-APIC-level eth1 106: 75901 0 PCI-MSI eth0 177: 3613 1 IO-APIC-level uhci_hcd:usb4, HDA Intel 185:4454030 1 IO-APIC-level uhci_hcd:usb3, nvidia 193:4509386 1 IO-APIC-level uhci_hcd:usb1, ehci_hcd:usb5, nvidia NMI: 0 0 LOC: 18436414 18436413 ERR: 0 MIS: 0 This lockup does not occur when using the UP 386 kernel (linux-image-2.6.15-28-386),but then, of course, only one of both CPU cores is used, wasting 50% of the CPU power. Installing the latest version (100.14.12 )of the nvidia driver from the nvidia website by means of 'envy' also solves the problem. Since 6.06LTS is supposed to be supported till 2009 I would urge you to include the latest nvidia proprietary driver in
[Bug 132400] Re: 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system
Since this bug is related to 6.06LTS (Dapper) the module version should be 2.6.15 instead of 2.6.22 ** Changed in: linux-restricted-modules-2.6.15 (Ubuntu) Sourcepackagename: linux-restricted-modules-2.6.22 = linux-restricted-modules-2.6.15 -- 6.06LTS: Computer locks up with nvidia proprietary driver on SMP system https://bugs.launchpad.net/bugs/132400 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
