seems installing evolution-indicator solves it without re-compiling ...
closing the bug as invalid ...
** Changed in: evolution (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in
** Attachment added: "evo-counter.png"
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1877852/+attachment/5369430/+files/evo-counter.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
Public bug reported:
Evolution has the ability to show the unread messages count in the Dock
app icon, this works for the Ubuntu Dock GNOME extension as well as for
Dash to Dock and indeed the old unity7 dock ...
simply re-compiling the current focal evolution package with an added
libunity-dev
the requirement for policykit (and dropping of gksu/gksudo) came with
the switch to gnome upstream, its a hard requirement for the desktop
nowadays.
while the default here might be wrong (and should be reviewed by someone
from the desktop team), this is definitely not a snapd related bug. i
added
> Now that Ubuntu has given up on Wayland by default
Ubuntu has not given up on Wayland by default but delayed it by one more
LTS (particulary because of bugs like this one).
Wayland by default is still the plan for the next LTS (and the interim
releases between 18.04 and 20.04). The incentive
feel free (i set the snappy task to fix-released too)
** Changed in: snappy
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1619258
Title:
** Summary changed:
- Networkd fail to set ip address between leases if ip address changes
+ Networkd fail to set ip address between leases if ip address changes on
UbuntuCore
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snappy
please note that this rule will also likely be used inside the initrd to
set up the console for encyption key input and there will be no systemd
around ... you probably want to rather handle it conditionally so it is
still available when creating an initrd ...
--
You received this bug
might be that we need it on Ubuntu Core (and server) though ... so
installing the rule at all should probably be conditional ...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1710637
*** This bug is a duplicate of bug 1708569 ***
https://bugs.launchpad.net/bugs/1708569
** This bug has been marked a duplicate of bug 1708569
1st. login fails to create a complete $HOME directory in a ubuntu-wayland
(defacto default) session
--
You received this bug notification because
*** This bug is a duplicate of bug 1708569 ***
https://bugs.launchpad.net/bugs/1708569
** This bug has been marked a duplicate of bug 1708569
Installer on latest image fails to create a complete $HOME directory
--
You received this bug notification because you are a member of Ubuntu
xdg-user-dirs normally runs on first login to create these dirs, not an
installer issue ...
** Also affects: xdg-user-dirs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you
looking at the listing as well as the fact that the syslog excerpt on
the forum is full of:
Apr 28 09:36:48 ci-comp11-dut systemd[1]: Started Session 1816 of user
root.
this is either a systemd bug or a bug with the way systemd is used in
the CI ... moving it to systemd to have a systemd
note that i see the non-starting wayland session on a 16.04 system that
does not have the unity8-desktop-session package installed, x11 gnome as
well as unity (7) start just fine and there is no trace of any unity8
packages on this laptop.
--
You received this bug notification because you are a
** Changed in: snappy
Status: New => Incomplete
** Changed in: snappy
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1620559
Title:
Public bug reported:
we currently have no working resolver on snappy installs,
/etc/resolv.conf is the boilerplate one.
on the low level we seem to have DNS from the DHCP server though
ogra@localhost:~$ grep -r DNS= /run/systemd/netif
/run/systemd/netif/leases/3:DNS=217.237.150.115
Public bug reported:
when removing a snap package gvfs shows a device in the unity panel for
a split second while the squashfs is unmounted during package removal.
ideally gvfs should ignore all snap package operations since the package
mounts should never be used directly by users.
running in
not sure if the fix for this needs to be in gvfs or in snapd, so i added
a snapd bugtask as well.
** Description changed:
when removing a snap package gvfs shows a device in the unity panel for
a split second while the squashfs is unmounted during package removal.
ideally gvfs should
hmm, this bug seems ot have been dragged away from the actual topic by
the audience, please note that this bug talks about phone and tablet
installs (as the "Canonical System Image" task implies) where we use a
reduced and slightly different installation compared to desktops (and
definitely no
if you have issues with evolution-data-server on a desktop install your
chances are way higher to have some desktop people look at it if you
file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in
Ubuntu)
Status: New => Fix Released
** Changed in: livecd-rootfs (Ubuntu)
Importance: Undecided => Medium
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Oliver Grawert (ogra)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whic
** Also affects: systemd
Importance: Undecided
Status: New
** Project changed: systemd => snappy
** Changed in: snappy
Importance: Undecided => Medium
** Changed in: systemd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
Public bug reported:
booting a snappy system which comes with a readonly file system that
carries /etc/mtab as pre-created link in the readonly area of the fs
(pointing to /proc/mounts), we always get an error message on boot when
systemd-tmpfiles tries to re-create the mtab link.
@lucio i only was commenting on the screenshot, the only way to end up
without the "HERE" option there is if you flashed a community image
instead of the stable or rc-proposed one. this UI option is tied
directly to the existence of the HERE AGPS backend existing on disk, if
this is not there you
@lucio, are you sure you are using the official stable (or rc-proposed)
channel for your device ? note that the dialog (and the HERE backend) is
only available in the right channels (i.e. the ones that get shipped on
the devices with a paid license), it is not in the community builds
(i.e. the
-team)
Status: Confirmed
** Affects: location-service (Ubuntu)
Importance: High
Assignee: Oliver Grawert (ogra)
Status: Confirmed
** Package changed: location-service (Ubuntu) = canonical-devices-
system-image
** Also affects: location-service (Ubuntu)
Importance
** Changed in: location-service (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1447110
Title:
location service fills disk with
** Changed in: cmpc
Status: In Progress = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/258110
Title:
Camera application cannot record video
To manage
http://paste.ubuntu.com/7234228/ has a potential fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1306515
Title:
Location detection no longer working
To manage
: Undecided = Critical
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) = Oliver Grawert (ogra)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1306515
Title
i can confirm ths behavior on a mako (nexus 4) too
** Also affects: indicator-bluetooth (Ubuntu)
Importance: Undecided
Status: New
** Changed in: phablet-tools
Status: New = Invalid
** Changed in: indicator-bluetooth (Ubuntu)
Status: New = Confirmed
** Changed in:
** Changed in: ubuntu-touch-meta (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1235419
Title:
seed should not include
** Changed in: android (Ubuntu)
Status: New = Fix Released
** Changed in: android (Ubuntu)
Assignee: (unassigned) = Oliver Grawert (ogra)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https
The problem here is that the USB Vendor and DeviceID are the same in
Ubuntu Touch and in android (we use the same kernel so the device
identifies itself the same way). Unlike android Ubuntu Touch doesn't
ship and MTP userspace bits which makes the mount fail. I would expect
gvfs to notice that and
** Summary changed:
- please add an option to inhibit gvfs mtp mounts
+ gvfs should not attempt to mount MTP devices in an endless loop (cluttering
your desktop with messages)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in
Public bug reported:
trying to use phablet-flash in raring to flash a phone or tablet (or
when just running adb shell or adb root from commandline) causes a
constant reconnect loop of an attached mtp device. it seems adb and gvfs
try concurrently to establish a connection which results in
so analyzing this a bit deeper, it actually does not have anything to do
with adb but with the fact that gvfs assumes that if an USB device
registers with:
Product: Android
Manufacturer: Android
(seen in dmesg)
gvfs blindly assumes there is mtp support on the other side ... Ubuntu
Touch
the mtp functionallity seems to be defined in
/lib/udev/rules.d/69-libmtp.rules, a quick and hackish workaround for
affected people using Ubuntu Touch would be to move this rules file out
of /lib/udev/rules.d/ (note that this indeed suppresses all mtp support)
--
You received this bug
a new ubuntu-defaults-nexus7 with luxd removed was uploaded ... please
check if the issue still persists on the recent nexus7 images
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = Invalid
** Changed in: unity-greeter
Status: New = Invalid
** Also affects:
this bug pre-dates the inclusion of luxd, luxd is just an interim
solution while the function is added to gnome-settings-daemon properly
(with a checkbox to allow manual vs auto-setting of the backlight)
fixes to luxd are indeed welcome in the interim ...
--
You received this bug notification
-acceld_start XSession.d file this enables auto-rotation of
the screen. it can be disabled by editing /etc/default/acceld
-- Oliver Grawert o...@ubuntu.com Mon, 21 Jan 2013 16:48:47 +0100
** Changed in: ubuntu-nexus7
Status: Triaged = Fix Released
--
You received this bug notification
could someone from the desktop team explain the reason why lightdm uses
the evo calendar factory at all ? does not really seem necessary for
spawning a greeter ...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
hmm, is this actually the output of the demsg command or did you just
paste /var/log/dmesg (note they are significantly different, the file in
/var only contains a boot snapshot of dmesg adn isnt useful for info
about issues on the running system)
--
You received this bug notification because
what you are doing is a pretty huge task for a 512M device that runs a
an ubuntu desktop already. i would assume you simply run out of ram
here, can you try to reproduce the crash and attach the full output of
the dmesg command to this bug ? i bet there will be a bunch of OOM
messages.
--
You
Public bug reported:
during image testing, apport popped up, wanting to submit this report
...
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: gnome-settings-daemon 3.4.2-0ubuntu2
ProcVersionSignature: Ubuntu 3.4.0-201.6-omap4 3.4.0
Uname: Linux 3.4.0-201-omap4 armv7l
ApportVersion:
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1010008
Title:
gnome-settings-daemon crashed with SIGSEGV on quantal armhf install
To manage notifications about this
moving the bug to the right package, metacity is responsible for the
window frames in unity-2d
** Also affects: metacity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: metacity (Ubuntu)
Status: New = Confirmed
** Changed in: unity-2d (Ubuntu)
Status: Confirmed
~/.xsession-errors shows the following line:
(gnome-power-manager:1051): GLib-GObject-CRITICAL **: g_object_unref: assertion
`G_IS_OBJECT (object)' failed
unity-2d-panel: [WARNING] libindicator: Unable to load icon from file '.
GThemedIcon battery-low-symbolic gpm-battery-020 battery-low '
** Also affects: gnome-power-manager (Ubuntu Oneiric)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/798546
Title:
No
@Daniel, no idea, i don't personally see it here (note that i haven't
touched gnome-power-manager in years, so i cant tell if there were code
changes that would touch this area)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
this bug has two tasks which arent reflected here, both tasks were fixed
...
** Also affects: unity-2d (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-2d (Ubuntu)
Status: New = Incomplete
** Changed in: unity-2d (Ubuntu)
Status: Incomplete = Fix Released
) = Oliver Grawert (ogra)
** Changed in: metacity (Ubuntu Natty)
Milestone: None = ubuntu-11.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
https://bugs.launchpad.net/bugs/759646
Title:
The capture before
uploaded to lucid-proposed
--
gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch()
https://bugs.launchpad.net/bugs/626379
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu.
--
and you think that would be a good default for all gnome sessions the
users select on the netbook image ? could your mother handle that
intuitively ?
sorry, but i really think thats a corner case for advanced hackers, by
default maximus requires window picker to be installed, else usability
@garym, how wuld a user close their windows without window picker
installed ? we cant enable it by default in a gnome-session since it
removes all opportunities to close the window if window picker is not
there.
--
maximus should only run in netbook-session and not start in gnome-session
@garym: yes, please file a new bug for this, it will actually need code
changes in maximus to make it detect if the session it is run in
contains window picker, currently it is not that clever and will only
start in the session the /etc/xdg mechanism fires it up in
@martin: no this is not a
Release Note:
On the ARM preinstalled images there is a minimal desktop session you can
select from GDM.
Due to a bug in the tool maximus (bug 631696) windows in this session have no
frames and are
always started in full screen mode.
** Changed in: ubuntu-release-notes
Status: New =
** Summary changed:
- When using ubuntu-netbook beta image on OMAP, after switching to standard
desktop, apps show up maximized
+ maximus should only run in netbook-session and not start in gnome-session
** Also affects: ubuntu-netbook-efl-default-settings (Ubuntu)
Importance: Undecided
** Changed in: f-spot (Ubuntu Maverick)
Milestone: ubuntu-10.10 = None
--
F-spot crashed with Unhandled Exception: TagLib.UnsupportedFormatException
https://bugs.launchpad.net/bugs/620495
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
ok, setting to wontfix then
** Changed in: gst-plugins-good0.10 (Ubuntu Maverick)
Status: Confirmed = Won't Fix
--
Unused upstream files missing in the source package
https://bugs.launchpad.net/bugs/607709
You received this bug notification because you are a member of Ubuntu
Desktop
** Changed in: f-spot (Ubuntu Maverick)
Milestone: ubuntu-10.10-beta = ubuntu-10.10
--
F-spot crashed with Unhandled Exception: TagLib.UnsupportedFormatException
https://bugs.launchpad.net/bugs/620495
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Also affects: f-spot (Ubuntu Maverick)
Importance: Medium
Status: New
** Changed in: f-spot (Ubuntu Maverick)
Milestone: None = ubuntu-10.10-beta
--
F-spot crashed
https://bugs.launchpad.net/bugs/620495
You received this bug notification because you are a member of Ubuntu
@olivier: we need to talk to upstream about the reason for not putting
these files into the release tarball, if there are no blocking reasons
(i.e. legality, stability) we can indeed include these files but an
upstream comment why they do not ship them in their release is essential
here.
** Also
** Changed in: netbook-meta (Ubuntu Maverick)
Status: Fix Committed = Fix Released
--
system fails to launch netbook-launcher-efl on arm system
https://bugs.launchpad.net/bugs/600487
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: netbook-meta (Ubuntu)
Importance: Undecided
Status: New
--
system fails to launch netbook-launcher-efl on arm system
https://bugs.launchpad.net/bugs/600487
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: netbook-meta (Ubuntu Maverick)
Importance: Undecided = Medium
--
system fails to launch netbook-launcher-efl on arm system
https://bugs.launchpad.net/bugs/600487
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-session (Ubuntu Maverick)
Status: New = Fix Committed
--
system fails to launch netbook-launcher-efl on arm system
https://bugs.launchpad.net/bugs/600487
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
in: gnome-session (Ubuntu Maverick)
Milestone: None = maverick-alpha-3
** Changed in: gnome-session (Ubuntu Maverick)
Assignee: (unassigned) = Oliver Grawert (ogra)
** Changed in: gnome-session (Ubuntu Maverick)
Importance: Undecided = Medium
--
system fails to launch netbook-launcher-efl
yes, tormod is right, i'm hit by bug 565981
--
evolution-data-server consumes massive amounts of memory, invokes OOM killer
https://bugs.launchpad.net/bugs/563879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in
i also see pulse and rhythmbox being killed, and even gnome-session here
i skipped updating for about a week and have the issue since last update
yesterday.
funnily running terminal windows with top and htop dont actually show
any peak in memory usage while this happens.
i am using a -pae
i am not so sure it is actually evolution-data-server though, even after
issuing an evolution --force-shutdown i get OOM errors (most visible
in chromium by randomly turning tabs into Oh No pages) this happens
while only rhythmbox, xchat and three terminal windows are open
alongside chromium (with
o...@osiris:~$ dmesg|grep invoked oom
[267156.692588] rhythmbox invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0
[267156.800774] gconfd-2 invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0
[267173.400379] pulseaudio invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0
** Attachment added: full_dmesg.txt
http://launchpadlibrarian.net/44671304/full_dmesg.txt
--
evolution-data-server consumes massive amounts of memory, invokes OOM killer
https://bugs.launchpad.net/bugs/563879
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
confirming, i see the same after the theme upgrade
--
terminal settings messed up after upgrade due to forced profile change
https://bugs.launchpad.net/bugs/532511
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in ubuntu.
could it be that we are missing the hardware specific codecs to drive
specific parts of the DSP for certain formats on this ARM board ?
--
Sound not working in all apps on dove
https://bugs.launchpad.net/bugs/528524
You received this bug notification because you are a member of Ubuntu
Desktop
weird, i dont see it on imx51
--
nautilus assert failure: *** stack smashing detected ***: nautilus terminated
https://bugs.launchpad.net/bugs/512959
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in ubuntu.
--
desktop-bugs
ok, after a dist-upgrade i can confirm it.
during upgrade i got the packageset from http://paste.ubuntu.com/363941/
(not including nautilus though)
i'll try to downgrade package by package and see when it goes away
--
nautilus assert failure: *** stack smashing detected ***: nautilus terminated
Public bug reported:
Binary package hint: gdm
on a babbage2.5 board installed from lucid alpha1 (which works fine and
reliable directly after install) gdm dies after the latest updates.
** Affects: gdm (Ubuntu)
Importance: Undecided
Status: New
** Tags: armel
** Tags added:
running gdm from the tty login as well as adding a sleep 1 directly in
front of the exec gdm-binary line in /etc/init/gdm.conf fixes the
problem.
we seem to hit a race condition here, probably some prerequisite gdm
relies on is slower on armel than on other architectires (though the
overall
http://people.canonical.com/~ogra/95_suppress_umount_in_ltsp.patch is an
old patch i once added to nautilus to suppress the umount option on LTSP
desktops, surely nautilus has changed a lot since but the patch might
serve as a base for a new one.
--
nautilus file menu still has unmount volume
note that the sound is essential for visulally impaired people, its one
part of the accessibility improvements we have over other distros. it
should not be removed by default.
--
Cannot prevent login sound
https://bugs.launchpad.net/bugs/437429
You received this bug notification because you are
i added gnome control-center (which contains the display-properties)
though i dont think it brings its own icons but uses the ones provided
in the theme :)
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
display properties notification area icon
reopening ...
i am seeing this on armel imx51 on the installed system from the beta
image happens frequently (not each time) directly after booting. it
doesnt happen on the live image
** Changed in: gvfs (Ubuntu Karmic)
Status: Fix Released = Confirmed
--
gvfs-gdu-volume-monitor crashed
gdm (2.27.90-0ubuntu7) karmic; urgency=low
...
* debian/gdm.upstart: Do not start in single-user modes or when text is
given as a kernel command line option. This restores previous behaviour.
(LP: #431176)
...
this was uploaded shortly after alpha 6, can you check with a more
recent
setting to fix released status, the issue doesnt show up with recent
upstream and gcc 4.4
** Changed in: gnome-keyring (Ubuntu)
Status: Triaged = Fix Released
--
[arm] gnome-keyring-daemon eating 100% CPU at login in Jaunty
https://bugs.launchpad.net/bugs/328167
You received this bug
i revisited the issue today and tested the following:
* we noticed that the issue does not show up in karmic so i rebuilt the
2.27 version of gnome keyring in jaunty, the issue returned with the
newer version as well
* i rebuilt the 2.27 source in jaunty with karmics gcc-4.4, the issue
@maresh
no, there are no hardcoded dependencies beyond the basic boot setup, as long as
the fis partitioning is the same and initramfs is used as explained above there
should be no issues.
your description sounds like a race between kernel and hardware (timing issue)
...
my theory would be
i dont think the plain dd to the device will work,
http://people.ubuntu.com/~ogra/arm/babbage/redboot-install has a script
that slightly reflects how the bootloader is currently set up (still
work in progress, but i hope to integrate it in the reboot-tools package
in karmic which should make it
thanks a lot for the detailed description, that helps a lot to narrow
down the problem :)
sorry if i appear like a PITA, but i want to make absolutely sure we only have
a single point of change ...
running flash-kernel on teh installed system will have the same effect btw, we
eleminated the
so while debugging that issue on our side it seems that the MAC address
for eth0 isnt set at all ... that seems to be related to the issue
--
notification area applets crash on login
https://bugs.launchpad.net/bugs/392716
You received this bug notification because you are a member of Ubuntu
if you are only changing redboot but keep kernel and initramfs the same,
does it behave sanely ? i suspect there is either a kernel config option
missing or some service/device that is expected to start in initramfs
isnt available ...
also does ifconfig show you a running loopback device in the
one other (rather hackish) hint if you want to test a proper
kernel/initramfs setup as ubuntu uses it:
(well, one way would be to base on a ubuntu kernel package, add your
patchset and just build that, since this will call the proper
postinstall scripts, use the needed configuration options for
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
** Changed in: gnome-screensaver (Ubuntu Hardy)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
gnome-screensaver restores default color-correction settings
https://bugs.launchpad.net/bugs/33214
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
g-p-m always try to set the main policy to 'ondemand'
https://bugs.launchpad.net/bugs/152808
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
Pressing power button unlocks locked screensaver
https://bugs.launchpad.net/bugs/37350
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
Screen blanks when watching movies
https://bugs.launchpad.net/bugs/66257
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
Closing lid should not turn off external LCD
https://bugs.launchpad.net/bugs/23220
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
** Changed in: gnome-screensaver (Ubuntu)
Assignee: Oliver Grawert (ogra) = (unassigned)
--
no 'Settings' button in gnome-screensaver
https://bugs.launchpad.net/bugs/22007
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber
** Changed in: cmpc
Assignee: Oliver Grawert (ogra) = (unassigned)
--
Invalid user name is not filtered in login window.
https://bugs.launchpad.net/bugs/247513
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
** Changed in: cmpc
Assignee: Oliver Grawert (ogra) = (unassigned)
--
gdmsetup window is truncated by low resolution screen.
https://bugs.launchpad.net/bugs/247501
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs
1 - 100 of 441 matches
Mail list logo
