This seems more like a server issue. I think it could easily be possible for
the server to guarantee that XIDs are not reused within a certain time period
since it issued a DestroyNotify. That won't guarantee that clients are happy,
but it can certainly help. We just need to store a
This is just how selections work. If the application is closed, there's nobody
to ask for the data. If you want this to work right, use a clipboard manager.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report
No response. Closing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/106060
Title:
[r128 1002:5446] Selecting the Molecule screensaver makes the PC
freeze. It is
I don't see how this could be happening in xorg-server ... my guess is
that it is kernel related.
Keith, can you comment?
Nicolo, are you still experiencing with newer kernels? Can you attach
system information:
lspci -v
dmesg
/var/log/Xorg.*.log
etc
--
You received this bug notification
Deferring to 1.13 as this is functional change
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/36812
Title:
Keyboard layout change on hotkeys press instead of release and do not
Lots of CCs ... I'm gonna bring this into the tracker to see if there's
something we can eventually do about this in a way that won't break backwards
compatibility.
Daniel, do you have any thoughts about how this could be done by extending XKB
rather than breaking it?
--
You received this
Confirmed fixed, thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/857159
Title:
nautilus launches indiscriminantly (it should not launch for xfce,
etc)
To manage
Public bug reported:
I just did a fresh install of 11.10 current (20110920 image and current repos).
I installed xubuntu-desktop.
When I login choosing xubuntu as my session type, nautilus is run even though I
would expect it not to. The nautilus desktop window covers my xfce desktop.
The
yes, it is still a problem with Gnome. XFCE's widget acts as expected
and is still a good work around.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
Architecture: powerpc
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1
PackageArchitecture: powerpc
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-powerpc
Uname: Linux 2.6.31-14-powerpc ppc
UserGroups:
--
[karmic regression] APM:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37894073/Dependencies.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/37894077/DevkitPower.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/37894086/GConfNonDefault.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/37894087/XsessionErrors.txt
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are
** Attachment added: gnome-power-bugreport.txt
http://launchpadlibrarian.net/37894088/gnome-power-bugreport.txt
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
** Tags added: apport-collected
--
[karmic regression] APM: gnome-power-manager does not recognize
Distro version: squeeze/sid
Kernel version: 2.6.31-14-powerpc
g-p-m version:2.28.1
HAL version: 0.5.13
System manufacturer: missing
System version: missing
System product: missing
AC adapter present: yes
Battery present: yes
Laptop panel present:
As mentioned, xfce notices the state correctly, so I believe it's a
problem with gpm or something that gpm depends on that xfce's power
manager doesn't
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
ping. This is a fairly annoying regression with Karmic/Gnome
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
I hit this a few months back, but I haven't seen the problem since...
--
gnome-power-manager crashed with SIGSEGV in __libc_start_main()
https://bugs.launchpad.net/bugs/376205
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
BTW, the XFCE Power Manager works as expected and properly detects the
state.
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
https://bugs.launchpad.net/bugs/414357
You received this bug notification because you are a member of Ubuntu
I was told that this isn't an issue in gnome-power-manager but probably
a misconfiguration in HAL, since gnome-power-manager is abstracted above
the APM/ACPI barrier... I have not confirmed this, however.
--
[karmic regression] APM: gnome-power-manager does not recognize state of
APM-only
** Summary changed:
- [karmic regression] gnome-power-manager does not recognize that powermac g4
is on battery
+ [karmic regression] APM: gnome-power-manager does not recognize state of
APM-only (non-ACPI) systems
--
[karmic regression] APM: gnome-power-manager does not recognize state of
Public bug reported:
Binary package hint: gnome-power-manager
gnome-power-manager reports that my PowerMac G4 is connected to AC when
in fact it is on battery. This is a regresison from Jaunty which
correctly reported its status and handled change to a low-power state.
jer...@aeris:~$ cat
powersaved works as a workaround for dimming the screen, etc ... but it
would be nice if gnome-power-manager could be updated to correctly show
the status.
--
[karmic regression] gnome-power-manager does not recognize that powermac g4 is
on battery
https://bugs.launchpad.net/bugs/414357
You
*** This bug is a duplicate of bug 223812 ***
https://bugs.launchpad.net/bugs/223812
Over a year later and still happening in jaunty and the current karmic
kernel (2.30-rc4 based)
--
powernowd init script does not start the daemon on ppc (ondemand problem)
*** This bug is a duplicate of bug 223812 ***
https://bugs.launchpad.net/bugs/223812
And this isn't a bug with powernowd. This is a kernel bug... please
change the component appropriately.
--
powernowd init script does not start the daemon on ppc (ondemand problem)
26 matches
Mail list logo