I verified the SRU by installing the gnome-shell from proposed,
42.5-0ubuntu1. The test succeeded.
I followed the test cases in
https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell.
For the test case 1, I couldn't notice any problem in any of the 4
sessions, with moving windows, tiling, appli
The color distortion resulting from this change is very glaring; not
even close to accurate color. So either this change should be fixed,
reverted, or color management should be disabled by default. All of
these solutions are simple; the broken attempt at color management is
not.
--
You received
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1950040
Title:
Wayland Screensharing broken
Public bug reported:
I was just resizing Seahorse's window in a clean Kinetic VM and it
segfaulted.
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: seahorse 42.0-2
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic x86_64
NonfreeKernelModules: zfs zunico
** Attachment added: "journalctl.log"
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1998484/+attachment/5633735/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in Ubuntu.
https://bugs.launch
Public bug reported:
1. Launch a terminal
2. Launch something from it, say 'xlogo &'
3. Put xlogo always on top by right clicking its title bar and selecting that
option.
4. Back to the terminal, open a new window, preferentially something whose lack
of input focus is evident, e.g. 'zenity --pas
Public bug reported:
These are the steps that I used to reproduce the issue:
Open Seahorse and click the entry below the passwords tab (in my system
it's called "Login"). Now,
snap install --stable chromium
snap connect chromium:password-manager-service
snap run chromium
Nothing new show
** Changed in: evolution (Ubuntu)
Assignee: Nathan Teodosio (nteodosio) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1983794
Title:
Evolution not delet
Test summary
Sorry but the test case is unclear to me. I don't consider it has
succeeded, I think some steps may be missing.
Test description
Started Jammy virtual machine, logged in with normal user, installed gdm
from jammy/proposed (42.0-1ubuntu7.22.04.1), opened
Public bug reported:
In Kinetic -- server + gnome package + nautilus/kinetic-proposed package
+ reboot -- under Qemu I often get segfaults when trying to
move/maximize Nautilus.
This is without ubuntu-desktop package so I'm not sure as to whether
such a configuration is supported.
ProblemType: B
** Attachment added: "Nautilus crash file"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654401/+files/lac2
** Tags added: apport-collected
** Description changed:
In Kinetic -- server + gnome package + nautilus/kinetic-proposed package
+ reboot -- under Qe
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2011589/+attachment/5654403/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2011589/+attachment/5654404/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https:/
** Attachment removed: "Nautilus crash file"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654401/+files/lac2
** Attachment removed: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654404/+files/ProcCpuinf
** Attachment added: "Stacktrace"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654417/+files/Stacktrace
--
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/
** Attachment added: "ThreadStacktrace"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654419/+files/ThreadStacktrace
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.la
--
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/2011589
Title:
Segfault when trying to move/maximize window
To manage notifications about this bug go to:
https://bugs.launchpad.net
** Attachment added: "StacktraceTop"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654420/+files/StacktraceTop
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpa
** Attachment added: "StacktraceSource"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2011589/+attachment/5654421/+files/StacktraceSource
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.la
Public bug reported:
I click a mountable volume in the Gnome dock, gnome-shell starts
consuming 100% CPU and also it misbehaves: New windows don't show up, if
you try to logout via upper-right corner > Log out it doesn't show the
log out dialog.
Killing it twice restores a working session.
After
** Description changed:
I click a mountable volume in the Gnome dock, gnome-shell starts
consuming 100% CPU and also it misbehaves: New windows don't show up, if
you try to logout via upper-right corner > Log out it doesn't show the
log out dialog.
Killing it twice restores a working
** Tags added: rls-ll-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2013070
Title:
100% CPU after clicking a mountable in the dock
To manage notifications about this
Public bug reported:
Single clicking the title bar of windows without a complex title bar
(namely a title bar with additional buttons besides the
close/maximinze/minimize) does not transfer focus to them.
I can reproduce this in my main, up to date Lunar system in Xorg and
also in a virtual machi
** Description changed:
Single clicking the title bar of windows without a complex title bar
(namely a title bar with additional buttons besides the
close/maximinze/minimize) does not transfer focus to them.
+
+ Reproduction recipe:
+
+ 1. Open gnome-terminal.
+ 2. Run xedit.
+ 3. Focus gn
Public bug reported:
Some custom shortcuts with super key will not work. The failing ones I
found:
Super + {1..9}
--
These will say
> Super+{Number} is already being used for Activate favorite app 9. If
you replace it, Activate favorite app 9 will be disabled.
That is not what happ
I can verify that in Bionic (with the deb) the application shows in
Gnome's task bar as a separate application, not grouped under Chromium,
and that in Lunar (with the snap) it shows in Gnome's task bar grouped
under the Chromium button.
However,
1. Wmctrl shows that the window classes and nam
** Attachment added: "xprop"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007652/+attachment/5664802/+files/google-chat.xprop
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.l
** Changed in: chromium-browser (Ubuntu)
Importance: Low => Medium
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad
> This bug is not fixed. Still happening for me in Xorg on Mantic.
The fix works for me (mutter 44.1-1ubuntu1).
Did you log out?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/201321
Jeremy Soller's fix to edit Xwrapper seems to be good.
The edits to the gdm service cause a crash to happen on boot.
Currently using an HP Laptop with an Intel CPU and Nvidia GPU that I
believe is Optimus.
I have the proprietary Nvidia driver running on nvidia-driver-430 as of
this comment's dat
Public bug reported:
Using `gdm` or `lightdm` and choosing gnome/xorg gives me a fatal error:
Oct 24 00:40:31 AS-XPS-13-9360 gsd-xsettings[2395]: You can only run one
xsettings manager at a time; exiting
Oct 24 00:40:31 AS-XPS-13-9360 gsd-xsettings[2395]: Failed to start: Could not
initialize x
Sure!
** Attachment added: "today.j"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1850125/+attachment/5301725/+files/today.j
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Public bug reported:
NetworkManager's copious syslog output is for some reason making its way
into my /var/log/kern.log file. This includes a couple dozen
lines at startup and a similar amount when connecting to WiFi with DHCP.
The NM man page states that the default facility should be DAEMON, a
I didn't get the error on login today which I think was due to
software/upgrade updates yesterday. Problem solved for me! Thanks
community.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpa
Many thanks, your last comment saved me a few hours ! Did you opened an
issue with gnome-keyring ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in Ubuntu.
https://bugs.launchpad.net/bugs/1573619
Title:
Signing with GPG
Public bug reported:
In Ubuntu 14.04 and earlier, gnome-terminal's transparent background
option works well with gnome-session-flashback and a non-compositing
window manager. I actually use xmonad, but metacity --no-composite shows
the same behavior: instead of real transparency, the portion of th
Nevermind, it looks like support for background images in terminal
widgets has been removed altogether, as explained here-
https://bugs.launchpad.net/terminator/+bug/1635704
** Changed in: gnome-terminal (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
Public bug reported:
I don't think it's just me, as I'm able to reproduce this on 2 physical
systems as well as a vanilla qemu/kvm instance, immediately after fresh
installs from both ubuntu-16.04.1-desktop-amd64.iso and ubuntu-16.04.2
-desktop-amd64.iso
When I run 'sudo init 1' or 'sudo telinit
This is actually getting worse in Debian stretch, and there affects
almost 2 dozen packages, so it might not even be the packages'
(NetworkManager, gnome-session) fault. Anyway, https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=858399
** Bug watch added: Debian Bug tracker #858399
http://bugs.
** Summary changed:
- NM and gnome-session seem to be syslogging with facility KERN
+ journald forwards to syslog with facility=KERN on everything
** Package changed: gnome-session (Ubuntu) => systemd (Ubuntu)
** Bug watch added: github.com/systemd/systemd/issues #5640
https://github.com/syst
** Bug watch added: Debian Bug tracker #837893
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893
** Also affects: systemd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837893
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
** No longer affects: network-manager (Ubuntu)
--
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/1613751
Title:
journald forwards to syslog with facility=KERN on everything
To manage
Public bug reported:
Keep getting system error to report following upgrade
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gnome-media 3.4.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
Uname: Linux 3.13.0-39-generic i686
ApportVersion: 2.14.1-0ubuntu3.5
Archit
fixed since 14.10, i believe?
** Changed in: ubuntu-gnome
Status: Confirmed => Fix Committed
** Changed in: gdm (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: ubuntu-gnome
Status: Fix Committed => Fix Released
** Changed in: gdm (Ubuntu)
Status: Fix Commi
Public bug reported:
I have a fresh install of Ubuntu 15.04 and am attempting to install
autofs.
$ sudo apt-get install autofs
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
autofs
0 upgraded, 1 newly instal
Public bug reported:
I have a fresh install of Ubuntu 15.04 and am attempting to install
hplip and the associated plugin(s) for my printer/scanner (HP LaserJet
Pro CM1415fnw color MFP).
After installing hplip, hplip-dbg, hplip-doc, and hplip-gui, I ran hp-
setup, selected my printer (connected vi
** Package changed: systemd (Ubuntu) => hplip (Ubuntu)
--
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/1476011
Title:
hp-setup plugin file does not match its checksum
To manage not
** Package changed: systemd (Ubuntu) => autofs (Ubuntu)
--
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/1475990
Title:
autofs service fails to connect to upstart
To manage notifica
Seeing on 15.10 as well, killall pulseaudio also fixes.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-media in Ubuntu.
https://bugs.launchpad.net/bugs/775345
Title:
USB headset not selectable in Output tab of Sound Preferenc
Since the patch attached in the bug report hasn't been accepted upstream
(and probably won't ever be), can we please add it to the Debian
packaging?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https
I decided to take some initiative and apply the patch myself. Naturally,
it needed to be applied to both gnome-settings-daemon and unity-
settings-daemon. The new setting is exposed at "org.gnome.settings-
daemon.plugins.sound.volume-step" and can easily be changed with dconf.
I've uploaded the pa
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
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/871133
Title:
Ubuntu Oneric
** Branch linked: lp:~george-edison55/gnome-settings-daemon/871133
--
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/871133
Title:
Volume Step not changeable in Unity an
Oops - I meant to write "If so" instead of "If not" in the fourth
paragraph of the last message.
--
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/871133
Title:
Volume S
"...just attached the patch done by Nathan Osman"
I didn't create the patch either, though I did need to tweak it a bit to
fix some compilation errors.
"First I see reports (mostly in the upstream report) that people are
getting 10-30% steps in volume instead of the defin
Public bug reported:
nathan@netbook:~$ sudo apt-get install libpoppler-qt5-1
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the
Your theory appears to have been correct. libpoppler68 is now appearing
as version 0.57.0-2ubuntu4
Apologies if the bug was unnecessary. I didn't realize this scenario
could occur in the archives.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
Public bug reported:
Installed blender from Thomas Schiex ppa: https://launchpad.net/~thomas-
schiex/+archive/ubuntu/blender
shared-mime-info didn't get configured on install, and apt -f install
reported that configuration was incomplete.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package:
Public bug reported:
Updated today, it moved from
2018-03-26 08:11:25 upgrade gnome-keyring:amd64 3.27.4-2ubuntu1
3.28.0.1-1ubuntu1
to
2018-03-26 08:14:34 status installed gnome-keyring:amd64
3.28.0.1-1ubuntu1
After this, noticed that some local code that uses ssh key comments
(from 'ssh-add
Public bug reported:
Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
font (e.g. ProFont). Desktop crashes; the new font does appear in the
apport dialogs, but attempting to log back into the session, xfde
** Also affects: gtk+2.0 (Arch Linux)
Importance: Undecided
Status: New
** Also affects: xfdesktop
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.l
** Description changed:
Reproduce: In Xubuntu (xfce), go to Settings Manager -> Appearance ->
Fonts -> Default Font, select an installed fixed-width, bitmapped .pcf
font (e.g. ProFont). Desktop crashes; the new font does appear in the
apport dialogs, but attempting to log back into the se
** Changed in: gnome-software (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1581713
Title:
Ubuntu Software asks for an Ubuntu S
This behavior is consistent with Ubuntu Software Centre. Canonical
works with third-party software providers to provide payment and hosting
for commericial software in the partner repository. In Ubuntu 16.04
LTS, this is being replaced by the Ubuntu App Store which powers the
snap repository's ba
This can easily be fixed by editing the gnome-panel.desktop file
`sudo vim /usr/share/applications/gnome-panel.desktop`
Move the first line ("X-Ubuntu-Gettext-Domain=gnome-panel-2.0") that
appears before the group name '[Desktop Entry]' to some point after, for
example mine now looks something li
Did it for me after a simple reboot. No monitors or other display
alterations.
--
gnome-panel assert failure: gnome-panel: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
https://bugs.launchpad.net/bugs/514914
You received this bug notification because you are a member of
Workaround appears to be 'ssh-add -d' to remove the dynamically added
identities - it then seems to reload from identity file and includes the
key comment.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https:
Update - that ssh-add -d did not actually work. It appears that it does
get the 'ssh-add -l' output back to correct, but any attempt to actually
USE the agent immediately re-adds the entry with only the filename/path
as the comment.
--
You received this bug notification because you are a member o
I have confirmed that overwriting gnome-keyring-daemon with an older
version from ub16 does return the behavior to expected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/17589
I was able to reproduce the problem by having both the Ubuntu and GNOME
session.
1. Login with Ubuntu session
2. Select the Dock settings panel
3. Logout, then back in with GNOME session
4. Launch gnome-control-center
It will try to open back the (now non-existent) Dock settings panel and
SEGFAUL
Not knowing the codebase, and going with the data != NULL assertion
shown with the crashes, it seems #7's link points to the fix.
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desk
I think it may have something to do with the gtk header bar, considering
how the problem (at least in my case) applies to Nautilus, the browser
previously known as Epiphany, the gnome core application Documents, as
well as the gnome core application Photos; these applications all use
the gtk header
https://www.youtube.com/watch?v=CFdllltkd98
** Summary changed:
- Nautilus unmaximised directory windows have a 50 pixel barrier from top panel
+ Unmaximised windows that use the gtk header bar have a barrier above them
preventing them from touching the top panel
** Description changed:
- Open
I've noticed that someone has updated the bug description such that it
says Nautilus isn't effected by the bug when it is being run as root, or
sudo. I'd just like to point out the reason; the version with root
privileges does NOT use the gtk header bar, this further supports the
idea that it is in
** Changed in: ubuntu-gnome
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1310322
Title:
Unmaximized windows that use the gtk header bar have a barrier
another work around: http://www.webupd8.org/2014/08/how-t...ient-
side.html
so far as I can tell, it removes the thing that makes the problem to
begin with, but it also removes the gtk header bars.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
This is increasingly curious...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1310322
Title:
Unmaximized windows that use the gtk header bar have a barrier above
them preventing the
The same problem doesnt happen moving header bar windows underneath
other windows.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/1310322
Title:
Unmaximized windows that use the gtk he
For those that are winding up at this bug report from searches looking
to resolve the problem - regardless of platform, here's a quick "fix":
* Move the keys out of ~/.ssh
* gnome-keyring-daemon -r -d
It's certainly not an actual fix, but will at least resolve the
immediate annoyance.
More i
@manzdagratiano I had the same symptom (but without mixed jaunty/karmic
sources).
It turned out to be caused by a rogue evince installation in /usr/local
What I did to track this down (in a terminal):
1. Verify these versions match:
for f in evince libevview1 libevdocument1 ; do apt-cache show
I just did a fresh install of Ubuntu 9.10 64 bit. My gdm is not
starting at boot. I took my nVidia graphics card out 8800 GTS and this
became a problem in i386 install. I did a fresh install today and now I
in the new install gdm is still not launching. I am using Nvidia
chipset MCP51. Graphics
yeah 9.10 and I get the google chrome error, changning permissions and
owners of the file did nothing. This is pretty lame.
--
Evince unable to open external links from pdf files
https://bugs.launchpad.net/bugs/223768
You received this bug notification because you are a member of Ubuntu
Desktop B
** Also affects: yelp (Ubuntu)
Importance: Undecided
Status: New
--
"Repeat the search online" does not work
https://bugs.launchpad.net/bugs/388750
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bug
** Also affects: ubuntu-website
Importance: Undecided
Status: New
--
"Repeat the search online" does not work
https://bugs.launchpad.net/bugs/388750
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to yelp in ubuntu.
--
desktop-bu
Public bug reported:
Binary package hint: evolution
Ubuntu Release: 8.10
Package Version (evolution): 2.24.3-0ubuntu1
Expected Behavior: Clicking on Mailbox shows a list of mail.
What happened instead: Nothing is displayed. Status message at bottom of window
indicates "Generating message list."
** Attachment added: "evolution backtrace"
http://launchpadlibrarian.net/22447828/gdb-evolution.txt
--
Evolution hangs on "Generating message list" with GroupWise account
https://bugs.launchpad.net/bugs/327683
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Thank you for the quick response and advice. I am having a little
difficulty generating the backtrace for evolution-data-server. I can
successfully attach to the process and duplicate the hang in evolution,
but when I press Ctl-C in the gdb (using instructions here:
https://wiki.ubuntu.com/Backtrac
I can confirm this bug on a Dell Inspiron 6000 laptop running Jaunty.
After adjusting the screen brightness using Fn+Up or Fn+Down, I am no
longer able to use the keyboard until switching to a TTY and then back
to X.
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided => Medium
** Attachment added: "uname.txt"
http://launchpadlibrarian.net/19980500/uname.txt
--
Partial keyboard and touchpad failure in X after changing screen brightness
https://bugs.launchpad.net/bugs/301351
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: "lspci.txt"
http://launchpadlibrarian.net/19980539/lspci.txt
--
Partial keyboard and touchpad failure in X after changing screen brightness
https://bugs.launchpad.net/bugs/301351
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/19980549/dmidecode.txt
--
Partial keyboard and touchpad failure in X after changing screen brightness
https://bugs.launchpad.net/bugs/301351
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
Same problem with a fresh install of Intrepid on an x60s.
The gconf editing solution from w1zard
(https://bugs.launchpad.net/ubuntu/+source/gnome-
session/+bug/290204/comments/12) does not work for me, but the
blacklisting solution of Vytas
(https://bugs.launchpad.net/ubuntu/+source/gnome-
session
I don't think this will have anything to do with the shutdown beep,
however it looks like some may just have the problem of disabling the
system bell all together.
It may be important to note that if any of you are using Compiz, you
will have to disable the system bell through the "CompizConfig Se
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Sorry, I only now had a moment to test this.
And [drum roll]
It worked perfectly.
Thanks!!!
--
Cannot install f-spot extensions
https://bugs.launchpad.net/bugs/231483
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop
This is still a problem with Jaunty:
(3) --> Request 145.0 QueryVersion (RANDR)
major_version 1
minor_version 3
(3) --> Request 145.8 GetScreenResources (RANDR)
window0x59
(3) <-- Reply to Request 145.0 QueryVersion (RANDR)
sequence #8 (578)
major_version 1
minor
201 - 300 of 577 matches
Mail list logo
