This issue was fixed in systemd by
https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that
change into 245.4-3, so Debian bullseye and buster-backports have the
fix, as does Ubuntu 20.04 (focal).
--
You received this bug notification because you are a member of Ubuntu
Bugs,
First message in second seat greeter log file is logged after less
than 1 second when I log in in first seat. At this moment greeter
starts eating cpu.
Please attach a debugger and get a stack trace when this happens.
Does the greeter crash, exit, or move to the background?
Greeter
In addition to the stack traces, please collect the following
information (before logging in via unity-greeter, so use Ctrl-Alt-F1
to log in via a VT or ssh into the machine)
Attached zip with files
Nothing looks strange there.
Please get a stack trace, either by looking at the core file
@a7x, I use Ubuntu 12.04.2.
Unfortunately, the multiseat PPA doesn't contain packages for 12.04
(precise). Multiseat requires logind, and that wasn't introduced to
Ubuntu until 13.04 (raring).
This PPA focuses only on support multiseat?
Yes.
Do it keeps sync with the mainstream in other
** Bug watch added: Red Hat Bugzilla #902301
https://bugzilla.redhat.com/show_bug.cgi?id=902301
** Also affects: fedora via
https://bugzilla.redhat.com/show_bug.cgi?id=902301
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
Raring and saucy packages containing the patch have been uploaded to the
multiseat PPA: https://launchpad.net/~ubuntu-multiseat/+archive/ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1209008
Raring and saucy packages containing the fix have been uploaded to the
multiseat PPA: https://launchpad.net/~ubuntu-multiseat/+archive/ppa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1201122
No joy for me, Pauli. I tried simply copying the firmware included
with the new driver into /lib/firmware/rtlwifi and verified the SHA1
sum matched the one you listed. I rebooted the machine (to avoid
dealing with any rmmod/modprobe shenanigans) and continue to see
~10% packet loss due to
But maybe you have some ideas where or what we need to fix?
A potential conflict with PAM settings was my best idea, but that
doesn't seem likely anymore.
I was able to login in both seats two times today, but I have no
idea what could caused that
Interesting! That could indicate a race
1) All greeters works fine until I login in one of all seats, it
does not matter which one.
1.1) When it is done remaining unity-greeters starts eating cpu.
Are any messages being logged over and over when it does this?
Next time it enters an infinite loop, please see if you can attach
** Also affects: unity-greeter (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/1201122
Title:
Remember last logged in user for each seat
To
Patched xorg with this
(https://bugzilla.redhat.com/attachment.cgi?id=751266action=diff)
patch from this
(https://bugzilla.redhat.com/show_bug.cgi?format=multipleid=962907)
bug report. And now lightdm shows up on second seat. Calvin Morrow
says that fix probably even simplier, read comment
If I try to change user on second seat when first seat user is
already loged in,
How were you able to get a user logged in to both seats? I thought
that the password prompt issue only made it possible for one user to
be logged in at a time. Are you doing auto-login?
second seat turns black
Public bug reported:
From https://bugs.freedesktop.org/show_bug.cgi?id=66851:
I have a multiseat setup with a primary on-board Intel graphics
device and a secondary Silicon Motion SM501 graphics card. My SM501
is configured via custom xorg.conf with siliconmotion ddx driver, so
it exposes no
).
** Changed in: lightdm
Assignee: a7x (a7x) = (unassigned)
** Changed in: lightdm (Ubuntu)
Assignee: a7x (a7x) = (unassigned)
** Changed in: lightdm
Status: In Progress = Confirmed
** Changed in: lightdm (Ubuntu)
Status: In Progress = Confirmed
** Branch unlinked: lp
(continuing the conversation from bug #976124 here since this bug report
seems more relevant)
but there were problems - huge memory leaks. In attached zip are log
files for xorg and lightdm. My .xsession-errors was full of error
lines:
dconf-CRITICAL **: unable to create file
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997483
Title:
VT_WAITACTIVE does not work well
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/977547
Title:
doesn't switch to graphical VT when auto
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/976124
Title:
lightdm multiseat: no login possible
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
To manage
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1075125
Title:
Multiseat: only first seat session
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085841
Title:
Add basic systemd-logind multiseat
*** This bug is a duplicate of bug 977547 ***
https://bugs.launchpad.net/bugs/977547
** Branch linked: lp:~a7x/lightdm/multiseat
** Branch unlinked: lp:~a7x/lightdm/multiseat-bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Sounds to me like there's a bug in your udev rules. Does:
udevadm info --export-db
show the tags and ID_SEAT variable set like you expect?
Other comments:
* You don't need a udev rule to assign something to seat0.
Everything is assigned to seat0 by default.
* Probably unrelated
Also tried to start x:
sudo X -core -config xorg-seat1.conf -sharevts :1 -auth
/var/run/lightdm/root/:1 -nolisten tcp -novtswitch -seat seat1
X server dosn't start - Fatal server error: (EE) no screens
found(EE)
After that:
sudo X -core -config xorg-seat1.conf -sharevts :1 -auth
Another thing you could try is assign everything to seat1 and see
if you can get just seat 1 to start:
99-multiseat.rules:
TAG==seat, ENV{ID_SEAT}=seat1, TAG+=seat1
TAG==seat, DEVPATH==/devices/pci:00/:00:1c.0/:02:00.0/*,
TAG+=master-of-seat
lightdm.conf:
1. [...] The common solution, found in proprietary solutions like
Userful Multiseat and Windows Multipoint Server, to do the right
seat assignment for input devices is an interface of kind
Please press Fx key in the keyboard in front of this display,
where x is 1 for the first seat, 2 for
** Tags added: multiseat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/861171
Title:
Shutdown from greeter does nothing when multiple accounts open
To manage notifications about this bug go to:
bug #1190581).
** Summary changed:
- Add compatibility with systemd-logind (for better multiseat support)
+ Add basic systemd-logind multiseat support
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lightdm
Assignee: (unassigned) = a7x (a7x
** Branch linked: lp:~a7x/ubuntu/saucy/lightdm/multiseat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085841
Title:
Add basic systemd-logind multiseat support
To manage notifications about
I have uploaded the package in the linked bazaar branch to my PPA
(https://launchpad.net/~a7x/+archive/multiseat) along with some
backported saucy packages for improved logind support in raring. To
install:
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt-get
PPA
(https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt-get upgrade
More complete instructions can be found by visiting the PPA page.
** Branch linked: lp:~a7x/lightdm/multiseat
** Also affects: lightdm (Ubuntu
** Changed in: lightdm
Status: New = In Progress
** Changed in: lightdm (Ubuntu)
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1085841
Title:
Add basic
of LightDM in my PPA
(https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt-get upgrade
More complete instructions can be found by visiting the PPA page.
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status
share that VT. LightDM doesn't currently support
this, but I have some changes to LightDM in progress to add more
complete multiseat support. If you are using Ubuntu, please try
installing the version of LightDM in my PPA
(https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository
with the
-sharevts argument. LightDM doesn't currently support this, but I have
some changes to LightDM in progress to add more complete multiseat
support. If you are using Ubuntu, please try installing the version of
LightDM in my PPA (https://launchpad.net/~a7x/+archive/multiseat):
sudo apt
** Tags added: multiseat
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/812170
Title:
Request support for unhandled (no greeter) sessions
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 977547 ***
https://bugs.launchpad.net/bugs/977547
** This bug has been marked a duplicate of bug 977547
doesn't switch to graphical VT when auto login is turned on, (multiseat)
--
You received this bug notification because you are a member of Ubuntu
PPA
(https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt-get upgrade
More complete instructions can be found by visiting the PPA page.
** Also affects: lightdm
Importance: Undecided
Status: New
** Changed
I have some changes to LightDM in progress to add more complete
multiseat support. If you are using Ubuntu, please try installing the
version of LightDM in my PPA
(https://launchpad.net/~a7x/+archive/multiseat):
sudo apt-add-repository ppa:a7x/multiseat
sudo apt-get update
sudo apt
I believe 73-seat-late.rules is from the systemd-services package, so
adding the systemd source package to the 'affects' list.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Oops, didn't see that it was changed from systemd to udev. Sorry for
the noise.
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175044
Title:
udevd[491]:
I just noticed that some of my gnome-settings-daemon crashes (~2 or 3
per day) have been BadWindow errors. I doubt gnome-settings-daemon uses
any KDE libraries. Could this bug be unrelated to KDE? (If so, it
looks like KDE apps tickle the bug more reliably than other apps.)
--
You received
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1198080
Title:
Krusader crashes after pressing F5 or ESC
To manage notifications about this bug go to:
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197879
Title:
krusader crashes with BadWindow - invalid Window parameter
To manage notifications about this bug go to:
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197679
Title:
Krusader crashes when closing certain popups with embedded terminal
emulator open
To manage notifications
*** This bug is a duplicate of bug 1197879 ***
https://bugs.launchpad.net/bugs/1197879
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197937
Title:
Krusader crashes
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195007
Title:
kile crashes when click on file new + save
To manage notifications about this bug go to:
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1114198
Title:
[power]: gnome-settings-daemon crashed with signal 5 in _XReply()
To manage notifications about this bug go
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176862
Title:
awesome crashes when using awful.util.spawn() on startup
To manage notifications about this bug go to:
** Tags added: badwindow
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1107926
Title:
bamfdaemon crashed with signal 5 in _XReply()
To manage notifications about this bug go to:
What do you mean by losing track of sessions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1192842
Title:
logind loses track of sessions when multiple sessions share a VT
To manage notifications
About a month ago I started getting BadWindow errors with konsole and
amarok, so I think it's a problem with some KDE library, not kdevelop.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1178843
Attached is a debdiff for Raring that is based on
https://bazaar.launchpad.net/~mar-kolya/compiz/fix-
for-1158267/revision/3734 (from the bzr branch lp:~mar-kolya/compiz
/fix-for-1158267). I have uploaded the patched package to my PPA
(https://launchpad.net/~a7x/+archive/bug1158267). To install
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1195384
Title:
problem with
wrong package (dash is the Debian Almquist Shell, not the Bourne-Again
Shell)
** Package changed: dash (Ubuntu) = bash (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100871
Title:
BASH
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1176394
Title:
dash working
See http://pubs.opengroup.org/onlinepubs/9699919799/utilities/cd.html,
specifically step 8.b.ii.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194800
Title:
cd flibbleflob/.. works when it
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1191567
Title:
UX - click on
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089747
Title:
Need setting
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007501
Title:
Applications
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1020218
Title:
keyboard not
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/972635
Title:
Firefox
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1078532
Title:
Dash does not
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002677
Title:
Dash finds but
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1019488
Title:
cannot drag
wrong package (dash is the Debian Almquist Shell, not the Unity Dash)
** Package changed: dash (Ubuntu) = unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/970357
Title:
Dash scope bars
Still a problem in raring.
** Changed in: dash (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165042
Title:
dash shell stdin handling not POSIX
To
This is not a bug --
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html says
that echo should process the backslashes. It would be a bug if echo did
not process the backslashes.
If you don't want backslashes processed, use printf:
printf %s\\n '\\'
** Changed in: dash
Public bug reported:
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sh.html#tag_20_117_06
says:
The standard input shall be used only if one of the following is true:
* The -s option is specified.
* The -c option is not specified and no operands are specified.
* The script
also affects emacs24
** Also affects: emacs24 (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/949126
Title:
[Regression] X resources take no
Attached is a script I wrote to make it easier to unlock systems from
remote. It works on precise and quantal even with the original
plymouth. I haven't tried the script on raring yet.
** Attachment added: script to automate unlocking of a system from remote
It has not yet been fixed in Raring. Precise, Quantal, and Raring are
all at 2.1.10, so the attached upstream patch should apply cleanly to
Raring.
I will edit the bug description according to the SRU procedure.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
+ [Impact]
+
Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
There is another bug where Pidgin users won't be able to log in if there
are multiple virtual hosts and the hostnames in the SRV records for the
two XMPP hosts are different.
-
I have removed the version I made from my PPA. Please downgrade to the
officially supported version now that a fix has been released.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048142
Title:
@bradleydsmith: Sounds like you're experiencing a different bug. You
may want to file a new bug report for it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041063
Title:
mouse pointer
@unwrecker and @alexandervolfman: This bug has been fixed and so this
bug report won't be reopened. However, a regression with similar
symptoms has appeared in 12.10 (Quantal). See bug #1063617.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Package changed: ubuntu = mythtv (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1029723
Title:
mythlogserver crashed with SIGSEGV in QObject::disconnect()
To manage notifications about
Looks OK to me, except for a minor issue in debian/changelog: LP:
1041063 should be LP: #1041063 (notice the missing #).
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Bug #1048634 fixes some Pidgin digest-uri check failures, but not all.
There is another bug where Pidgin users won't be able to log in if there
are multiple virtual hosts and the hostnames in the SRV records for the
two XMPP hosts are different.
For example, suppose
Upstream bug report (launchpad doesn't recognize it, so I can't use Also
affects project):
https://support.process-one.net/browse/EJAB-1578
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097366
Attached is a debdiff that includes the upstream patch. I've been
running with the upstream patch for months now without any problems.
** Patch added: debdiff for precise
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+attachment/3477236/+files/debdiff-precise.patch
** Tags
** Patch added: upstream patch
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1097366/+attachment/3477243/+files/ejab-1578.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097366
@Dan: I believe you are experiencing a different but similar bug --
please open a new bug report. (Even if it is the same bug, it is likely
caused by a regression and should thus have a new bug report. But
either way, this bug is marked as fixed and will therefore be ignored
by Ubuntu
Tagging with regression-release because this works in 12.04. Thanks to
@Dr_Jekyll for testing!
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1088081
Title:
udev
Public bug reported:
http://launchpad.net/ubuntu/+source/xorg-server/2:1.11.4-0ubuntu10.10
was uploaded to precise-proposed supposedly to fix bug #1041063.
However, the version of xorg-server in precise is unaffected by that bug
so the change should not be necessary.
** Affects: xorg-server
filed regression-proposed bug #1091976
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041063
Title:
mouse pointer periodically leaps to left and top of screen with
absolute pointing devices
To
** Changed in: rlinetd (Ubuntu)
Status: Confirmed = Invalid
** Summary changed:
- atftpd does not install correctly
+ atftpd fails to install -- update-inetd doesn't like udp4
** Summary changed:
- atftpd fails to install -- update-inetd doesn't like udp4
+ atftpd postinst should pass
As I noted before in comment #25, this bug was introduced upstream in
1.13. Precise has version 1.11.4, so it should not be affected. How
can something be fixed if it is not broken?
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification
.
I uploaded the modified cairo package to my PPA
(https://launchpad.net/~a7x/+archive/bug1043769) and it has finished
building. To install:
sudo apt-add-repository ppa:a7x/bug1043769
sudo apt-get update
sudo apt-get upgrade
** Patch added: debdiff for cairo (quantal)
https
And here is the debdiff for gnome-control-center (against the quantal
version).
For gnome-control-center, I applied the following patches:
http://git.gnome.org/browse/gnome-control-center/commit/?id=c1857b0f9c80434890679ace83865db5d2565fa6
** Description changed:
+ [Impact]
+
+ Users with multiple displays are unable to change display settings
+ (arrange displays, change resolutions, change the primary display, etc.)
+ with 'gnome-control-center display' unless they happen to know to switch
+ focus to another window and switch
*** This bug is a duplicate of bug 1043769 ***
https://bugs.launchpad.net/bugs/1043769
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #1043769, so it is being marked as such. Please
** Bug watch added: GNOME Bug Tracker #681475
https://bugzilla.gnome.org/show_bug.cgi?id=681475
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=681475
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
I believe the following upstream patches will fix this (I have not tried
them yet):
http://git.gnome.org/browse/gnome-control-center/commit/?id=c1857b0f9c80434890679ace83865db5d2565fa6
http://git.gnome.org/browse/gnome-control-center/commit/?id=a61f0654b98357283ef68bea6d827aabc0a2779e
The cairo bug report is linked because apparently the fix for the gnome-
control-center bug exposed a bug in cairo. I'm not sure if quantal
already has that cairo fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The quantal version of cairo does not have the fix referenced above, so
I'm marking this bug report as also affecting the cairo package.
** Also affects: cairo (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Additional cairo patches needed:
http://cgit.freedesktop.org/cairo/commit/?id=df6780442feba5c0c9404353177f24913b58bd32
http://cgit.freedesktop.org/cairo/commit/?id=08e3f4614b688331534d72f46c9c3e9f292d0216
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Running 'vgchange -a n volume_group_name' generates udev events that are
matched by /lib/udev/rules.d/85-lvm2.rules, causing it to run 'vgchange -a y'.
This defeats the initial 'vgchange -a n' and makes it impossible to:
* run 'cryptsetup luksClose' on the underlying
** Also affects: udev (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/1088081
Title:
udev rules make it impossible to deactivate lvm volume group
1 - 100 of 537 matches
Mail list logo
