Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
@Hui, the user states it's a regression, what changed? did we use to
list cards without an output connected?
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => High
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notific
** Changed in: ubuntu-themes (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transparency/graph
When you get the issue is "systemctl suspend" successful at suspending?
Can you give the output of the "systemd-inhibit --list"?
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Invalid
** Summary changed:
- Laptop does not suspend after lid is closed
+ Laptop does not suspend after lid
Sorry for the confusing and thanks for reporting upstream!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1760246
Title:
nautilus does not obey display order after keyboard-find
Sta
Added an im-config task but I don't know how that could trigger
graphical problems.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transpar
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down y
Looks like they are already discussing the issue on
https://gitlab.gnome.org/GNOME/nautilus/issues/385
** Changed in: nautilus (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
htt
@Hui, I have disconnected and reconnected the speakers when plugging
back the acquisition board
The strange part is that I had two systems installed on two different
partitions. By just booting on a system I had the sound or not.
If I understand well that would mean it is an issue with the speake
The X error (from comment #3) is:
#3 0x7f5a769377f7 in g_log_structured (log_domain=0x7f5a7365304e
<_gdk_wayland_display_utf8_to_string_target+270>
"f\220I\213U\bH\215J\001I;M\020s\"I\213u", log_level=G_LOG_LEVEL_ERROR) at
../../../../glib/gmessages.c:1768
args = {{gp_offset = 48,
Thank you for your bug report. Could you add a screenshot to the bug
showing the issue?
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
You are right about the macro including new versions, that at least
explains why it makes a difference.
Then that patch was dropped 3 years ago in Debian and in fedora:
https://src.fedoraproject.org/cgit/rpms/ibus.git/tree/ibus.spec#n715
It's unclear why it would need to be restored now. It looks
Could you include the journal log or look if you stop gnome-software &
start it again from a command line then if it prints out
errors/warnings?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launch
It's another instance of bug #1620806 - just triggered differently.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to im-config in Ubuntu.
https://bugs.launchpad.net/bugs/1760818
Title:
gedit and gnome-calculator transparency/graphics co
Could you include the journal log after getting the issue?
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Incomplete
--
You rec
Public bug reported:
After I updated to Ubuntu 18.04 I noticed that chromium interactions
(scroll for example) and mouse pointer itself started to freeze for
hundreds of milliseconds (0.1s - 0.2s).
So, I was constantly scrolling (in order to reproduce the bug) while
running perf top, and it point
I have just noticed that dmesg has very strange info:
WARNING: kernel stack frame pointer at b2107faf in chromium-browse:1892
has bad value 648ab7fa
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubun
Here's the crash with GDK_SYNCHRONIZE=1. It appears to be graphical. And
I have a theory this maybe only happens on machines that default to hi-
DPI (scale 200%) in the live session...
#6 0x7fffef656c8d in _XError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7 0x7fffef653bb7 in ?? () f
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
** Description changed:
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
+
+ ---
+
+ WORKAROUND:
+
+ 1. Boot into the live session.
+ 2. Settings > Devices > Displays > Scale = 100%
+ 3. Cli
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy network-manager
network-manager:
Installed: 1.10.6-2ubuntu1
Candidate: 1.10.6-2ubuntu1
Version table:
*** 1.10.6-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic
The attachment "The second patch for 18.04 after applying the Arch
patch" seems to be a patch. If it isn't, please remove the "patch" flag
from the attachment, remove the "patch" tag, and if you are a member of
the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed b
Public bug reported:
First time starting gnome-control-center after login, it takes
~70seconds to load and 100%CPU. Only first time starting I get
"nvc0_screen_create:906 - Error allocating PGRAPH context for M2MF:
-16".
In terminal "top" shows "gst-plugin-scan" is the offender. I installed
two e
I get this trying to use gnome-control-center under the "Gnome Classic"
session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1766799
Title:
gnome-control-center (ERROR
Thank you for your bug report. What do you mean exactly by the system hangs?
You can't interact with the launcher, switch softwares, etc?
Upstream has a report about keyboard navigation not working in settings when
orca is enabled, see
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/7
Thank you for your bug report. Could you look in the system monitor what
is using the CPU while it freezes? Would also be useful to maybe get a
backtrace (http://wiki.ubuntu.com/DebuggingProgramCrash ) of the
processes while it's hanging
** Changed in: gnome-control-center (Ubuntu)
Importance:
*** This bug is a duplicate of bug 1758120 ***
https://bugs.launchpad.net/bugs/1758120
** This bug has been marked a duplicate of bug 1758120
package gnome-split 1.2-1 failed to install/upgrade: trying to overwrite
directory '/usr/share/pixmaps' in package gnome-search-tool 3.6.0-2 with
n
Thanks, that's known upstream, see
https://bugzilla.gnome.org/show_bug.cgi?id=748476
** Bug watch added: GNOME Bug Tracker #748476
https://bugzilla.gnome.org/show_bug.cgi?id=748476
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center
It's similar to https://bugzilla.gnome.org/show_bug.cgi?id=794632 which
has been fixed in 3.28.1. There are a few reports from the new version
but it's not clear those are just not cases of users who had g-c-c open
before applying the update. Is anyone still having the issue with
3.28.1?
** Change
Same problem on Dell XPS 15 9560 with fresh install of Ubuntu 18.04 both
X and Wayland. Did not have issue on 17.10 (X) and 17.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bug
Could you get a valgrind log for the issue?
** Information type changed from Private to Public
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-c
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1766799
Title:
gnome-control-center (ERR
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-screensaver (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.lau
Stack trace with debug symbols (mostly).
** Attachment added: "dbg.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131299/+files/dbg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubu
** Package changed: gnome-control-center (Ubuntu) => apport (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1765667
Title:
[Feature Request] enhance Apport with a
This looks odd. We start with a 16x16 icon upscaled to 32x32
(scale=200%) but the pixbuf_x/y offset seems to be negative (memory
underrun?). Is that a faulty attempt at rendering 32x32 from 16x16
input?
#19 0x7fffef158e83 in INT_cairo_surface_create_similar_image
(other=, format=CAIRO_FORMAT_
Suspend works for me again, after adding "acpi_rev_override=1" with
"sudo nano /etc/default/grub" in: GRUB_CMDLINE_LINUX_DEFAULT="splash
acpi_rev_override=1 nouveau.runpm=0"
Then "sudo update-grub"
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
Ignore comment #16. Negative offsets appear to be valid:
https://developer.gnome.org/gdk3/stable/gdk3-Cairo-Interaction.html#gdk-
cairo-set-source-pixbuf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.laun
(In reply to David Dreggors from comment #45)
> This does not yet appear in updates-testing, should it?
Not yet. There will be an automated comment on this bug when it reaches
testing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnom
gnome-shell-3.28.1-3.fc28 has been pushed to the Fedora 28 stable
repository. If problems still persist, please make note of it in this
bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launch
In the meantime you can download it direct from Koji for testing, the
update page has a link through to the Koji build -
https://koji.fedoraproject.org/koji/buildinfo?buildID=1077605
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-s
gnome-shell-3.28.1-3.fc28 has been pushed to the Fedora 28 testing repository.
If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here:
This affects me too, 18.04 WPA2/PLEAP connect via phone tether OK but
fails as above directly, worked fine under 17.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Ti
So far gnome-shell-3.28.1-3.fc28 is looking good. :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1765261
Title:
[regression] Ubuntu 18.04 login screen rejects a valid password
This does not yet appear in updates-testing, should it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1765261
Title:
[regression] Ubuntu 18.04 login screen rejects a valid passwo
Discussed during F28 Go/No-Go meeting, acting as a blocker review
meeting: https://meetbot-raw.fedoraproject.org/fedora-
meeting-1/2018-04-26/f28-final-go-no-go-meeting.2018-04-26-17.02.txt .
It was generally felt that, while this is clearly a serious bug, it's
not actually going to significantly i
@Flavien,
According to the alsa-info.txt of #6 and #7， there is no speaker at all
on the 3 sound cards, if you mean there is indeed speaker on one of the
sound cards, that should be a problem of kernel driver.
So could you please install the ubuntu 18.04 (bionoic beaver) and test
if it has the sa
** Changed in: gnome-shell (Fedora)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1765261
Title:
[regression] Ubuntu 18.04 login scre
It's a shame this fix did not get through to 17.10, it effects a number
of cameras.
I'm crossing my fingers, is it fixed in 18.04?.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libgphoto2 in Ubuntu.
https://bugs.launchpad.net/bugs/173
Here it is
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1768137/+attachment/5131316/+files/journal.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon i
** Changed in: cups (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printin
@Daniel & Sebastien,
For the 1:8.0-0ubuntu3.8, the pulseaudio will regard the profile as
available even no output device is plugged, for 1:8.0-0ubuntu3.9, the
profile will be set to unavailable if there is no output device plugged.
The 1:8.0-0ubuntu3.9 has the same behaviour as the 17.10 and 18.
BTW.
Once I disconnect from the 4k monitor my cursor remains huge I tried to
take a screenshot but it doesn't take the cursor I took a picture of the
screen with my phone here they are
https://photos.app.goo.gl/2a28ZQw0JSSTRi242
--
You received this bug notification because you are a member of
** Description changed:
+ The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc).
+
+ ---
+
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
---
WORKAROUND:
1. Boot into
Looks like same as: https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1748839
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1761003
Title:
Bionic Beaver - not a
any update on this issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1370363
Title:
deja-dup fails to backup using SFTP/SSH if Gnome Keyring is not
available
Status in Déjà Du
@Hui,
I already checked on a live-usb of 18.04, this morning the sound is
working (it was not on Sunday morning).
It is definitely a speaker detection issue. It could come from the hardware as
well.
Anyway, I planned to install Ubuntu 18.04 to test it before upgrading my main
system next summer
Here's the offending source code up to the failing X call. I'm not so
sure that the math is right (or how getting it wrong might trigger this
bug)...
static cairo_xlib_shm_t *
_cairo_xlib_shm_pool_create(cairo_xlib_display_t *display,
size_t size, void **ptr)
{
Disp
@Hui,
I confirm, no more issue with Ubuntu 18.04, speakers and headphones are
correctly detected.
Thanks.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1767784
Title:
[regressi
Public bug reported:
When I log into my system I'm stuck at a black screen for a while. After
waiting about a minute gnome shell is loaded but as mainly frozen.
I guess it is an xorg problem, but I'm not at all sure about that.
It could also be a gnome-shell issue.
That happens since I updated f
Correction:
Possibly worth noting is that size==4096 at scale 200%, and size==1024 at scale
100%.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity
Dell XPS15 9560 - System is now usable, after nightmare of trials and about 50
reboots.
If I recall correctly: Ctrl-Alt-F2 / F3 on login prompt; sudo update; sudo apt
purge nvidia*; sudo apt install nvidia-390;
I switched to Wayland and back, all broken again, so then again in tty at login
pro
** Changed in: xkeyboard-config
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xkeyboard-config in Ubuntu.
https://bugs.launchpad.net/bugs/1635074
Title:
Nepali Keyboard symbol should have zero
I can no longer replicate this issue either.
The issue was appearing in Elementary OS rather than native Ubuntu.
The issue can probably just be closed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.lau
@Flavien,
Got it, thanks. Could you please take some time to generate an alsa-
info.txt under 18.04, let us see if it is a regression for pulseaudio
1:8.0-0ubuntu3.9.
If the speaker and headphone can't work under 16.04, it is really an
issue.
thanks.
--
You received this bug notification becau
Public bug reported:
lspci -nnk | grep -iA2 vga
00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ
Integrated Graphics Controller [8086:2772] (rev 02)
Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller
[103c:302a]
Kernel modules: i915, intelfb
One bug report should also describe one issues, it's not very practical
dealing with different issues at the same place
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/176539
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/G
@Hui,
I think there's a misunderstanding,
>From the moment I disconnected and reconnected the speakers everything is
>working well on all the versions I tested it on.
So from my understanding
- the speakers were working although not detected
- due to the update, when speakers are not detected th
*** This bug is a duplicate of bug 1735986 ***
https://bugs.launchpad.net/bugs/1735986
Thanks, the upstream report is the right thing to do, unsure why you got
asked to filed downstream as well but it's fine, we can watch what they
do from it
** Changed in: gnome-control-center (Ubuntu)
Im
*** This bug is a duplicate of bug 1735986 ***
https://bugs.launchpad.net/bugs/1735986
That's known upstream as well, see https://gitlab.gnome.org/GNOME/gnome-
control-center/issues/17
** This bug has been marked a duplicate of bug 1735986
Unable to set different scale correctly on differe
Upstream report https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/17
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => High
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a m
*** This bug is a duplicate of bug 1735986 ***
https://bugs.launchpad.net/bugs/1735986
Oh, you reported to github not on GNOME's gitlab which would be the
upstream location, sorry about the confused comment.
--
You received this bug notification because you are a member of Desktop
Packages,
> Here is built-in palette collected with gsettings get:
> ['#2E3436',
> '#CC',
> [...]
Could you please elaborate, what are the exact steps you took that gave
this result? What steps did you perform in gnome-terminal's Preferences
dialog, what additional scripts did you run (if any, e.g. Anth
Thank you for your bug report, do you try to use different scaling
factors for the screens? It looks like https://gitlab.gnome.org/GNOME
/gnome-control-center/issues/17
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1764876
Title:
gnome-control-center crashed with SIGSEGV in
gtk_stack_
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/G
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
the new version is in bionic
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1760005
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Attachment removed: "CoreDump.gz"
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
Thank you for your bug report, is that still an issue in 18.04? What
desktop environment do you use?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification b
The fix is in bionic
** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1757503
Title:
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1753070
Title:
Cannot restore default alert so
@Tom - I have the same exact machine. I tried each of your steps in
order, and I still get only a black screen boot with a few PCIe Bus
Errors. Did you perform a fresh install from scratch or was this coming
from an upgraded OS? Does that even matter???
--
You received this bug notification be
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
http://comments.gmane.org/gmane.comp.audio.pulseaudio.general/21051
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1741045
Title:
Change the default resample-method to speex-float-
Could you copy the output of "debsums gnome-control-center"?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packa
Could you try if that's still an issue in 18.04?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1744409
Title:
Unable to arrange displays in gnome control center with 3 c
Could you try if that's still an issue in 18.04?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which i
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Package changed: gnome-control-center
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1744719
Title:
gnome-control-center crashed with
** Summary changed:
- Automatic time zone not working
+ Automatic time zone not working when location disabled
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug
*** This bug is a duplicate of bug 1718727 ***
https://bugs.launchpad.net/bugs/1718727
** This bug is no longer a duplicate of private bug 1735763
** This bug has been marked a duplicate of bug 1718727
gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()
--
You rece
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1724894
Title:
gnome-control-cent
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
https://wiki.ubuntu.com/Bugs/Upstream/G
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?
This will help us to find and resolve the problem.
** Changed in: gnome-control-center (Ubu
** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1722186
Title:
/usr/bin/gnome-con
1 - 100 of 268 matches
Mail list logo
