@Gabriel
Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as
well.
linux-image-generic-hwe-20.04
5.11.0.27.29~20.04.11
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Public bug reported:
Description:Ubuntu Focal Fossa (development branch)
Release:20.04
ibus 1.5.22-2ubuntu1
Steps to reproduce
1. Upgrade to GNOME 3.36.0.
2. Restart Ubuntu 20.04 daily with Wayland
What did you expect to happen
The ibus daemon is launched.
What happened
I've verified trusty unity-control-
center14.04.3+14.04.20140922-0ubuntu1.1 from trusty-proposed archive,
verification-done.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is
@Alberto
It was originally a quick workaround for the possible race condition so
could you help to modify the code with what Iain had suggested? Totally
agree that making it asynchronous, adding more verbose log and finding
out the root cause are better ways to fix this issue.
--
You received
Public bug reported:
OEM LP private bug: https://bugs.launchpad.net/bugs/1466441
Title: Sometimes system turns a black screen when resume from S3 via Lid
Close
Summary:
Sometimes system turns a black screen when resume from S3 via Lid Close
It only has cursor on screen but still can switch to
** Description changed:
+ Trusty (and Utopic) SRU Request:
+
+ [Impact]
+
+ * Set higher priority of glxinfo's result then Xorg's log for Details
+ - Overview - Graphics info in Unity Control Center.
+
+ [Test Case]
+
+ * System with glxinfo installed (in mesa-utils) will show glxinfo's
+
Public bug reported:
In some of OEM's AMD platforms,
open System setting-Details-Graphics from control center,
find the Graphics Driver show VESA: XX strings ,
not as accurate as what glxinfo -l | grep OpenGL renderer string
shows.
The VESA: string displayed in System
** Description changed:
In some of OEM's AMD platforms,
open System setting-Details-Graphics from control center,
find the Graphics Driver show VESA: XX strings ,
not as accurate as what glxinfo -l | grep OpenGL renderer string
shows.
The VESA: string displayed in
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority/trusty
Importance: Undecided = High
** Changed in: oem-priority
Importance: Undecided = High
--
You
https://bugs.launchpad.net/bugs/1386620 this issue is fixed by Maarten
Lankhorst (mlankhorst) and the option will be re-enabled.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/131964
Title:
search for files.. entry in gnome-menu should launch tracker-search-
tool
Status in “gnome-panel” package in
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/131964
Title:
search for files.. entry in gnome-menu should launch tracker-search-
tool
Status in “gnome-panel” package in
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1035431
Title:
bluetooh-wizard failed to connect to
Public bug reported:
Touch screen and touchpad lost click function after quickly tapped dash
home repeatly by touch screen, Installed 14.04, still have same issue.
Quickly tapped dash home more than three times by touch screen.Found
touch screen and touchpad lost click function.
Note:
1.When
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Also affects: oem-priority/trusty
Importance: Undecided
Status: New
** Changed in: oem-priority/precise
Importance:
it also can reproduce in Unity 2D + 331.20 driver + nvidia-prime on
12.04 + Saucy LTS HWE stack. (3.11 kernel)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1210077
Title:
works fine to me with gnome-control-center/1:3.4.2-0ubuntu0.13.1 on
Precise.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Description changed:
+ [Impact]
+
+ * User can choose the suspend time and blank time in the gnome control
+ center (system settings).
+
+Also, there's a gsetting called org.gnome.settings-daemon.plugins.power
idle-dim-time which default in Ubuntu is 30 secs and will dim the screen
** Description changed:
[Impact]
- * User can choose the suspend time and blank time in the gnome control
- center (system settings).
+ According to the current design in Ubuntu Precise, users can choose the
+ suspend time and blank time in the gnome control center (system
+ settings).
** Description changed:
- Some Canonical OEM partners have requested additional options be added
- to the power option system sleep settings menu.
+ [Impact]
+
+ * Currently, the power option system sleep settings menu in Ubuntu precise
has the following options:
+5 minutes, 10 minutes, 30
Public bug reported:
Some Canonical OEM partners have requested additional options be added
to the power option system sleep settings menu.
https://launchpad.net/bugs/1238727
Currently, the power option system sleep settings menu has the following
options:
5 minutes, 10 minutes, 30 minutes, 1
** Patch added: oem-power-suspend-options.patch
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244065/+attachment/3889368/+files/oem-power-suspend-options.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Also affects: oem-priority
Importance: Undecided
Status: New
** Also affects: oem-priority/precise
Importance: Undecided
Status: New
** Changed in: oem-priority/precise
Importance: Undecided = Critical
--
You received this bug notification because you are a member of
And also set X-GNOME-Autostart-Phase=Initialization so the menu will not
have the entry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/951000
Title:
disable guest session screen
Since gconf is deprecated,
could we just modify /usr/sbin/guest-account ,
add an autostart script in the guest $HOME/.config/autostart/
and let gsettings set the correct default value for disable-lock-screen?
--
You received this bug notification because you are a member of Desktop
Packages,
check with fglrx 13.3 beta didn't fix the issue.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1080514
Title:
Click-and-drag in eye of gnome crashes X
Status in HWE Next
** Tags added: 201210-11863
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1134028
Title:
[Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for
Radeon HD 7600M
** Tags added: 201202-10593 taipei-lab
--
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/1076840
Title:
[CS4213, Dell Inspiron 3420] Internal speaker does not show up in
Sound
** Tags added: taipei-lab
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1086720
Title:
After installed of fglrx or fglrx-update, can't boot to desktop
Status in
** Changed in: fglrx-installer (Ubuntu)
Status: Incomplete = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/838659
Title:
[Inspiron M4110] can't output to
** Tags removed: cid201206-11396 cid201206-11418
** Tags added: 201206-11396 201206-11418
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1086720
Title:
After installed of
The system, Dell Precision M4700, still has the suspend problem with installed
ii nvidia-current-updates 304.64-0ubuntu0.1
NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-settings-updates304.43-0ubuntu0.2
Confirmed bug is fixed on my Vostro 2420.
--
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/946232
Title:
[Meta-bug] Missing speaker and/or internal mic port
Status in “pulseaudio”
We got some haswell platforms here and met same issues.
It keeps showing the warning
plymouthd: intel_bufmgr_gem.c:2783: drm_intel_bufmgr_gem_init: Assertion `0'
failed.
in the log,
however there's no such code in the libdrm-ltsq2.
Track it a bit It seems that libdrm-ltsq-intel1 didn't
system: 201205-11418(Dell Inspiron 14s) also affected by this bug.
** Tags added: cid201206-11396 cid201206-11418
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1086720
Title:
Hello,
I have tried two systems in our lab, but both of them have no built-in BT
module, so I can't verify this issue.
--
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/1038084
Title:
The bug is fixed with pulseaudio 1.1-0ubuntu15.2 under Precise.
--
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/1076840
Title:
[CS4213, Dell Inspiron 3420] Internal speaker does
I have verified it on Quantal, kernel 3.5.0-21.32, but bugs remains, internal
speaker interface disappears, but sound actually works.
@kentb: you want me to test with updated pulseaudio under Quantal? The
pulseaudio I installed on the system is 2.1-0ubuntu4.
--
You received this bug
I have the system, but it's still occupied by others, I will test the
system when it's available.
--
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/1038084
Title:
Bluetooth devices
this bug is fixed by installing package,pulseaudio-1.1-0ubuntu15.2.
I can see the mic interface now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1073420
Title:
[Dell Inspiron
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1073420
Title:
[Dell Inspiron One 2020] No Microphone
This bug is fixed with pulseaudio 1.1-0ubuntu15.2, the jack detection
works now.
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
After the linux-headers-3.5.0-17-generic installed and reinstalled fglrx
fglrx-amdcccle, system is able to boot to desktop without problem.
I see there're two problem.
1. It seems linux-headers-3.5.0-17-generic is not installed by default
2. The fglrx package finishes installation without the
3.5.0-20.31 has just been superseded by 3.5.0-20.32, I will test it when
3.5.0-20.32 is ready.
--
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/1076840
Title:
[CS4213, Dell Inspiron
Public bug reported:
System: HP Heineken 10 ( 201206-11396)
After installed of fglrx and fglrx, can't boot to desktop, only the background
and mouse pointer are shown.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-17-generic 3.5.0-17.28
ProcVersionSignature: Ubuntu
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1086720/+attachment/3452059/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
201206-11396 fails the suspend without fglrx. After fglrx installed, the
system can wake up from suspend, but still can't boot to desktop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
ii fglrx 2:9.000-0ubuntu3
amd64Video driver for the AMD graphics accelerators
ii fglrx-amdcccle2:9.000-0ubuntu3
amd64Catalyst Control Center for the AMD graphics
@diwic:
the 5 systems are currently we have tested and found the bugs. We will continue
to test more systems, if we found systems have this bug, I will comment on this
bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in
** Project changed: gvfs = gvfs (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1076835
Title:
[Dell Inspiron 4320]Bluetooth/browses-files doesn't work
Status in “gvfs” package
Public bug reported:
VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI
Wrestler [Radeon HD 6310] [1002:9802]
jockey.log is attached.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: jockey-common 0.9.7-0ubuntu7.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
** Bug watch added: GNOME Bug Tracker #688220
https://bugzilla.gnome.org/show_bug.cgi?id=688220
** Also affects: gnome-control-center via
https://bugzilla.gnome.org/show_bug.cgi?id=688220
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1055874
Title:
Automatic sleep settings are not
@sparhawkthesecond
what is your idle-delay ?
org.gnome.desktop.session idle-delay may affect on this.
as I said in #2, idle-delay setting must be same with
sleep-display-(ac|battery).
I think g-c-c UI have this check but if you use gsettings to cheange the value
then it may not that easy to
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=668703
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
** Project changed: gnome-settings-daemon = gnome-settings-daemon
(Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1055874
Title:
Automatic sleep settings are not
** Package changed: gnome-settings-daemon (Ubuntu) = gnome-settings-
daemon
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-power-manager
@Sparhawk
what's the result of
#gsettings get org.gnome.settings-daemon.plugins.power idle-dim-time
?
idle-dim-time will affect the time you set on those settings, you need
to plus the dim time.
if idle-dim-time is 30, and sleep-display-ac is 60
your monitor will turn off after 90 secs
@Sparhawk
and if your sleep-inactive-(ac|battery)-type is suspend
the actual suspend time will be
sleep-inactive-(ac|battery)-timeout + idle-dim-time
but if your sleep-display-(ac|battery) sleep-
inactive-(ac|battery)-timeout
the actual suspend time will be
sleep-display-(ac|battery) +
Public bug reported:
Open the system setting-Details-Graphics, find the Graphics Driver
show VESA: XX strings , not the accurate information from glxinfo -l
| grep OpenGL renderer string
The VESA: string displayed in System Settings--Details-Graphics is
because
gnome-control-center will
** Attachment added: gnome-control-center-graphics-info.patch
https://bugs.launchpad.net/bugs/1040456/+attachment/3272883/+files/gnome-control-center-graphics-info.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Tags added: cid201105-8043 taipei
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/869799
Title:
[Dell inspiron M5110] no output while external VGA is connected
** Tags removed: taipei
** Tags added: lab-taipei
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/869799
Title:
[Dell inspiron M5110] no output while external VGA is
The gsd-debug-randr.log while bug happened.
** Attachment added: gsd-debug-randr.log
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/869799/+attachment/2632778/+files/gsd-debug-randr.log
--
You received this bug notification because you are a member of Desktop
Packages, which is
The output log from xrandr.
log above is before the external display plugged, after
that is after external display connected.
-
If I connected the external monitor first, then boot the system. The external
display is ok.
If I switch to console
As I see from the xrandr.log, there is two preferred mode (1366x768,
1440x900, marked with +), but no current mode(marked with *).
CRT1: 1366x768@0 +1366+0 (Unknown)
Automatically configured outputs to deal with event
Got RANDR event with timestamps change=14722 config=160860
If I changed the mode with below command, the external display looks good. But
the bottom of main display of laptop will be cut-off.
xrandr --output --mode 1440x900.
mode 1366x768 is ok with command: xrandr --output --mode 1336x768.
No matter which mode it switched to, the external monitor can
67 matches
Mail list logo
