[Bug 640720] [NEW] Make Default button in Gnome Display Properties has no effect on the resolution at login screen
Public bug reported: Binary package hint: gnome-control-center My monitor's native resolution is 1440x900. I would Ubuntu's login screen to be at that resolution. The problem is that while I can select that resolution from Display Properties and it works when I'm logged in, the applet's Make Default button has no effect on the login screen, it comes up at 1280x1024. I'm running Ubuntu Maverick Meerkat, my video adapter is AMD/ATI Radeon 9800 pro and I'm using the open-source drivers. Here's a list of relevant software package versions: xserver-xorg-video-radeon-1:6.13.1-1ubuntu5 gnome-control-center-1:2.31.91-0ubuntu2 gdm-2.30.5-0ubuntu4 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: gnome-control-center 1:2.31.91-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4 Uname: Linux 2.6.35-21-generic i686 Architecture: i386 Date: Thu Sep 16 21:08:35 2010 ExecutablePath: /usr/bin/gnome-display-properties InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta i386 (20100901.1) ProcEnviron: LANG=et_EE.utf8 SHELL=/bin/bash SourcePackage: gnome-control-center ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick -- Make Default button in Gnome Display Properties has no effect on the resolution at login screen https://bugs.launchpad.net/bugs/640720 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 640720] Re: Make Default button in Gnome Display Properties has no effect on the resolution at login screen
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/640720/+attachment/1594811/+files/Dependencies.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/640720/+attachment/1594812/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/640720/+attachment/1594813/+files/ProcStatus.txt ** Attachment added: XsessionErrors.txt https://bugs.launchpad.net/bugs/640720/+attachment/1594814/+files/XsessionErrors.txt -- Make Default button in Gnome Display Properties has no effect on the resolution at login screen https://bugs.launchpad.net/bugs/640720 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310000] Re: Keyboard shortcuts don't stick with multiple keymappings
I disagree, for what it's worth. In #204202, the problem is with in- program shortcuts (ctrl+z to suspend current job in Terminal) working in an unexpected way while here we are dealing with desktop shortcuts (super+t to launch Terminal) not working. Perhaps the cause is the same or close enough, but wouldn't the symptoms have to be more similar in order to really call the bug reports duplicates? That's not a rhetorical question -- I actually don't, but would like to, know. -- Keyboard shortcuts don't stick with multiple keymappings https://bugs.launchpad.net/bugs/31 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 614176] Re: [855gm] 2.6.35-14: Invisible Cursor
I'm also affected by this bug when running Lucid Lynx with kernel 2.6.35-v9patch1.1 from Brian Roger's PPA for i845 and i855 freezing fixes. lspci -nn |grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) -- [855gm] 2.6.35-14: Invisible Cursor https://bugs.launchpad.net/bugs/614176 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310000] Re: Keyboard shortcuts don't stick with multiple keymappings
For the record, my workaround involves setting system and user layouts to be _different_ from each other. But that might be a moot point. I don't know what caused this (I don't remember doing anything other than installing chromium-browser and messing around with Gnome default browser setting), but the workaround stopped working, at least partially -- Metacity shortcuts work, g-s-d ones don't. Logging out and in again still hides the bug, so I will turn off autologin as another work-around for now. -- Keyboard shortcuts don't stick with multiple keymappings https://bugs.launchpad.net/bugs/31 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310000] Re: Keyboard shortcuts don't stick with multiple keymappings
It's interesting that you are hitting the bug without autologin. My theory so far has been that GDM does something to make the bug go away, but apparently that does not happen in your case. Maybe that's because we're using different versions? I'm running Lucid Lynx on my computer with GDM version 2.30.0-0ubuntu5, what about you? I don't think the distinction between US and UK QWERTY is particularly important. Where I mentioned standard US QWERTY, I was guessing that this would be the fallback / hard-coded keymap that erroneously gets used when triggering hotkeys. I think I'll leave figuring out a solution for people who know the inner workings of the software in question, but I did figure out a work-around that at least hides the problem in my case: I set my system keyboard layout to Estonia Dvorak and user's layout to Estonia Dvorak and Estonia US keyboard with Estonian letters. Whereas before both system and user's layouts were like the current user's layout, now they differ between themselves and the bug does not manifest. I hope this helps. -- Keyboard shortcuts don't stick with multiple keymappings https://bugs.launchpad.net/bugs/31 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 310000] Re: Keyboard shortcuts don't stick with multiple keymappings
I've researched this behaviour in some detail and would like to help in solving this bug. I would open a new bug in GNOME bugzilla, but I don't know what to file it against, so I'd like to discuss the bug here first. I have had this problem for a while and have even filed a couple of bug reports, but the conclusions I had drawn then were inaccurate. By using a more systematic approach to testing this and by actually writing down the results, I think I have narrowed the issue down quite a bit now, though. To reproduce this problem, all conditions have to be met: Use autologin. If you happen to log out and in again through GDM, the bug stops working and expected behaviour ensues. The first keyboard layout has to have keys that differ from those of standard US QWERTY keyboard, e.g. US Dvorak. That's where the symptoms arise -- shortcuts using these keys. The user's keyboard layout(s) have to exactly match (those of) the system's. In other words, after selecting the user's keyboard layout(s), apply the layout settings system-wide (there should be a button in keyboard preferences for that). The symptoms, should you get the above right: Shortcuts get triggered (the first step of two, if you will) when pressing the key combination as it would appear on QWERTY layout (expected behaviour: Dvorak keys should trigger the shortcuts). Then they get handled (step two) by either Metacity (e.g. run terminal) or Gnome-Settings-Daemon (e.g. run web browser). Metacity handles the key combination as if pressed on QWERTY, so the shortcut sort of works, it just isn't on the right key. G-S-D handles the key combination as pressed on whatever layout you are actually using, complicating matters. Generally the shortcut doesn't work, but it might, like in this example: You use Dvorak layout. You have ctrl+u set as shortcut 1 and ctrl+g (which corresponds to ctrl+u on qwerty) as shortcut 2. Shortcut 2 effectively works as expected. So, where should this bug go? As I said, I wouldn't mind reporting it in GNOME Bugzilla if I just knew what component to file it against. -- Keyboard shortcuts don't stick with multiple keymappings https://bugs.launchpad.net/bugs/31 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403303] Re: power manager reports 1% battery even though it is full on Asus Eee PC netbook
On my Eee PC 900 I have never experienced any unpredictable shutdowns, just the low capacity warning, but setting /apps/gnome-power- manager/notify/low_capacity to False gets rid of that. -- power manager reports 1% battery even though it is full on Asus Eee PC netbook https://bugs.launchpad.net/bugs/403303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518306] Re: Some keyboard shortcuts stop working after reboot when using non-qwerty layout
I'm still affected by this problem after switching to 10.04 Lucid Lynx (gnome-settings-daemon 2.30.0-0ubuntu1). -- Some keyboard shortcuts stop working after reboot when using non-qwerty layout https://bugs.launchpad.net/bugs/518306 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518306] Re: Some keyboard shortcuts stop working after reboot when using non-qwerty layout
** Description changed: Binary package hint: gnome-settings-daemon - When using Dvorak keymap, keyboard shortcuts that are handled by g-s-d - and have a letter in them (e.g. super+w, launch browser) don't work when - logging in. Resetting them either in Keyboard Shortcuts or gconf-editor - makes them work again. This bug does not affect shortcuts handled by - Metacity, hence I'm reporting it here and using the new custom shortcuts - feature in Keyboard Shortcuts as a workaround. + After logging in, all keyboard shortcuts have moved to the physical + positions of QWERTY layout, even though such layout is not used. - The problem is affecting gnome-settings-daemon 2.28.1-0ubuntu2 under - Ubuntu 9.10 + Versions affected: + gnome-settings-daemon 2.28.1-0ubuntu2 under Ubuntu 9.10 + gnome-settings-daemon 2.30.0-0ubuntu1 under Ubuntu 10.04 + + Steps to reproduce: + 1. Set keymap to Estonia Dvorak. + 2. Observe that pressing ctrl+alt+h (which translates to ctrl+alt+d on Dvorak keymap) hides all windows, given that ctrl+alt+d is set up to show desktop. + 3. Reboot. + 4. When logged in again, observe that ctrl+alt+h has no effect while ctrl+alt+d hides all windows. Note that this is not desired behaviour for a Dvorak keymap user. -- Some keyboard shortcuts stop working after reboot when using non-qwerty layout https://bugs.launchpad.net/bugs/518306 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518306] Re: Some keyboard shortcuts stop working after reboot when using non-qwerty layout
Actually, that's not true, that is, custom shortcuts do not necessarily
work.
To clarify: Shortcuts involving keys that differ on Dvorak and Sholes
layout do not work when system keymap is set to Dvorak. So, for
instance, alt+f4 works, as does ctrl+shift+m ('m' and 'a' are in the
same position on both Dvorak and Sholes layout). The latter is probably
where my confusion about custom shortcuts working arose from.
--
Some keyboard shortcuts stop working after reboot when using non-qwerty layout
https://bugs.launchpad.net/bugs/518306
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 518306] [NEW] Some keyboard shortcuts stop working after reboot when using non-qwerty layout
Public bug reported: Binary package hint: gnome-settings-daemon When using Dvorak keymap, keyboard shortcuts that are handled by g-s-d and have a letter in them (e.g. super+w, launch browser) don't work when logging in. Resetting them either in Keyboard Shortcuts or gconf-editor makes them work again. This bug does not affect shortcuts handled by Metacity, hence I'm reporting it here and using the new custom shortcuts feature in Keyboard Shortcuts as a workaround. The problem is affecting gnome-settings-daemon 2.28.1-0ubuntu2 under Ubuntu 9.10 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- Some keyboard shortcuts stop working after reboot when using non-qwerty layout https://bugs.launchpad.net/bugs/518306 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403303] Re: power manager reports 1% battery even though it is full
I have done some research on this problem and come across an informative discussion on this problem on a Debian-related mailing list: http://www.mail-archive.com/debian-eeepc-de...@lists.alioth.debian.org/msg01135.html What I got from this is: The Eee pc's battery does not adhere to ACPI standards in reporting its capacity, returning a percentage in a field which is specified as having the unit mAh. Linux (ACPI driver, I guess) exports the percentage value of capacity in mAh in /proc/acpi/battery (and possibly elsewhere), which leads into problems in anything that uses it. So where should this be fixed? Given that this has slim chance of happening in Eee pc's BIOS and no chance of everyone even upgrading to that unlikely new BIOS version, I would say the next best place would be just one step up the ladder -- in Linux ACPI driver -- because if this would be fixed (only) in devicekit-power, other processes that don't rely on dk-p, e.g. manually cat'ing /proc/acpi/battery/BAT0/info, would still return erroneous results. -- power manager reports 1% battery even though it is full https://bugs.launchpad.net/bugs/403303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 460631] Re: Incorrect warning about eeepc battery
*** This bug is a duplicate of bug 403303 *** https://bugs.launchpad.net/bugs/403303 ** This bug has been marked a duplicate of bug 403303 power manager reports 1% battery even though it is full -- Incorrect warning about eeepc battery https://bugs.launchpad.net/bugs/460631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417389] Re: [karmic] Can't connect w/ Option Globesurfer Icon 1.8Mbit/s 3G usb Modem
For what it's worth, I've noticed that it's not always the second attempt at connecting through NM that succeeds, it can be the third or fourth attempt. I only tried a couple of times without updates from NM PPA and can therefore not say for certain if it would have worked were I more persistent. -- [karmic] Can't connect w/ Option Globesurfer Icon 1.8Mbit/s 3G usb Modem https://bugs.launchpad.net/bugs/417389 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417389] Re: [karmic] Can't connect w/ Option Globesurfer Icon 1.8Mbit/s 3G usb Modem
I'm using Option GlobeSurfer Icon (0af0:6600 Option GlobeTrotter 3G+ datacard) and therefore am also affected by this bug. I can confirm that: - in plain Karmic, I can not connect using NM, not the first or any subsequent time I try. - in plain Karmic, I can connect by setting up /etc/ppp/peers/foobar (device /dev/ttyUSB0) and running sudo pon foobar. - with updates the NetworkManager PPA (https://launchpad.net/~network-manager/+archive/trunk) I can use NM to connect with success on the second try. Simone Tolotti has already provided logs from situation similar to mine, but let me know if my own particular logs would be of use, I'd be happy to run through DebuggingModemManager in that case. -- [karmic] Can't connect w/ Option Globesurfer Icon 1.8Mbit/s 3G usb Modem https://bugs.launchpad.net/bugs/417389 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311842] Re: Shift+Mod4+( doesn't work as a keyboard shortcut
Using gconf-editor, I manually edited a keyboard shortcut at /apps/metacity/global_keybindings to find out what key combination it is that gets compared to the shortcut when pressing the Shift, Mod4 and 9 key -- it is Shift, Mod4 and 9. -- Shift+Mod4+( doesn't work as a keyboard shortcut https://bugs.launchpad.net/bugs/311842 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311842] Re: Shift+Mod4+( doesn't work as a keyboard shortcut
I can confirm the bug on Karmic, specifically gnome-control-center
1:2.27.91-0ubuntu3. The problem, as far as I can understand -- and mind
you, this is mostly speculation -- is this:
At the time of keyboard shortcut assignment, all modifier keys and a
symbol is captured. In the non-working example above, what gets captured
is {Shift+Mod4+(}. '(' is, unfortunately, another way of saying
{Shift+9} (depending on the keyboard), so when keys get pressed at
another time, what gets compared to the shortcut above is either
{Shift+Mod4+9} or {Mod4+(}.
I guess whatever is making the comparison is case-insensitive or
something, because alphabetic keys work in Shift-combinations. *-key on
the number pad does not have a Shift-accessed secondary key, so this
works as well.
Does this seem plausible to anyone else or am I way off base here?
--
Shift+Mod4+( doesn't work as a keyboard shortcut
https://bugs.launchpad.net/bugs/311842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403303] Re: power manager reports 1% battery even though it is full
I can also confirm the bug, though I would like to suggest a more precise summary: Power manager reports 1% battery capacity on a working battery. I'm using Karmic desktop (a5 + updates) on an Eee PC 900. On boot, I always get the notification and sometimes a dialog box as well, but if I remember correctly, the dialog box does not have a button for ignoring the issue, I can post an update when I know for sure. It would be nice to be able to get rid of the message, nicer still if the battery information (or possibly misinformation) provided by Eee PC would be used in a way that would make sense. -- power manager reports 1% battery even though it is full https://bugs.launchpad.net/bugs/403303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 403303] Re: power manager reports 1% battery even though it is full
I can confirm that the occasional dialog box only has a close button. Here's a screenshot. ** Attachment added: Screenshot-Untitled Window.png http://launchpadlibrarian.net/31706291/Screenshot-Untitled%20Window.png -- power manager reports 1% battery even though it is full https://bugs.launchpad.net/bugs/403303 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269463] Re: visual effects revert on login
I was using g-c-c 1:2.23.90-0ubuntu9. After upgrading to -0ubuntu10, the problem seems to be gone. Thanks! -- visual effects revert on login https://bugs.launchpad.net/bugs/269463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269463] Re: visual effects revert on login
As an aside, the other problem I have (that I can't do multiple logins) is unrelated and still persists. I'll see if I can find/report it here on Launchpad. -- visual effects revert on login https://bugs.launchpad.net/bugs/269463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269777] [NEW] Blank screen on second login if user has Compiz enabled
Public bug reported: In my Intrepid Ibex system, in a situation where user A is logged in, user B is unable to use the system if user B has Visual Effects enabled (it doesn't matter whether user A does). It is possible for user B to log in, but the display remains pure white with the only visible thing being the cursor on it. It is possible to e.g. run a browser and resize it using feedback from the cursor to locate the edge of the browser, but that's not much of a use. Pressing ctrl+alt+backspace has the effect of showing the wallpaper and placeholders for panels for a split second, then logs out. If it is relevant, my computer has an Ati Radeon 9800pro video card and I am not using the proprietary drivers. Thanks for your time. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- Blank screen on second login if user has Compiz enabled https://bugs.launchpad.net/bugs/269777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269463] [NEW] visual effects revert on login
Public bug reported: In Intrepid Ibex, selecting None for visual effects in Gnome Appearance Preferences has no permanent effect -- it reverts to Custom (or nothing if you don't have certain compizconfig packages installed) on next login. The problem only concerns saving the changes between sessions -- during a session, visual effects can be switched properly. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- visual effects revert on login https://bugs.launchpad.net/bugs/269463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269463] Re: visual effects revert on login
I have fixed the problem on my system. Here's what I think caused it: I had upgraded from Hardy using update-manager -e (which, maybe, I should have mentioned in the original bug report) and apparently was left with some cruft that caused Compiz to misbehave. After completely removing and then reinstalling all packages related to Compiz, it is gone. Because Compiz misbehaved, I had another problem (which, of course, is gone now): Multiple users could not usably be (graphically) logged in at the same time, only the first login was functional. The other(s) would wind up with what looks like an empty screen and a cursor. So, what now? Should the bug be closed or can something be improved with the information I have supplied? -- visual effects revert on login https://bugs.launchpad.net/bugs/269463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 269463] Re: visual effects revert on login
Oops, it seems I was hasty with my conclusions and the bug is back, along with the multiple login inability of course. -- visual effects revert on login https://bugs.launchpad.net/bugs/269463 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
