Confirming that fix suggested by Zunda in the bug description works for
me on Ubuntu 20.04.2 LTS and LibreOffice Ubuntu package version:
1:7.1.1~rc2-0ubuntu0.20.04.1~lo1.
Below, the fix I repeated again just to make sure everybody understand
exactly what I did.
---
Adding templates file to ~/Templates works for Nautilus
1:3.36.3-0ubuntu1 (Ubuntu 20.04), but the right context menu is not
available if one has no more empty space left in the window to right
click (say when you display a directory with 50+ files in it).
My comment suggest probably another bug
It worked for me this morning with IntelliJ IDEA, Ubuntu 19.10, and the
following setup:
$ echo $XMODIFIERS
@im=ibus
$ java -version
openjdk version "11.0.5" 2019-10-15
OpenJDK Runtime Environment (build 11.0.5+10-b520.30)
OpenJDK 64-Bit Server VM (build 11.0.5+10-b520.30, mixed mode)
--
You
Thanks Daniel. I installed the following packages:
libjpeg-turbo8-dbg/eoan,now 2.0.3-0ubuntu1 amd64 [installed]
libjpeg8-dbg/eoan,now 8c-2ubuntu8 amd64 [installed]
libnvidia-gl-435 does not have any debugging symbols package available.
Next time it crashes, I will transmit a better report.
I have a crash report which was uploaded with apport on 2019-12-22 08:38
EST. The UUID for the crash report is: 59c38b68-24c0-11ea-b1ac-
fa163e983629
I am no expert, but it looks pretty similar to this report. Can someone
glance at it to confirm if it is the same problem or another?
@kenjo (ken-kenjo) found the solution for me. The error shows up every
second in syslog. However, when I quit the Gnome shell extension
'System Load Indicator 0.4', it stops.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This bug report expired because 17.04 is not supported anymore. Did
anyone recreate a corresponding bug report for a more recent version of
Ubuntu? If so, can you please publish the link so we can subscribe to
it?
--
You received this bug notification because you are a member of Desktop
Since I reinstalled Ubuntu 18.04, I do not have this problem anymore. I
believe that a bug still lay hidden somewhere but the conditions to
activate it is gone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
I confirm that since I installed xdg-utils 1.1.2-1ubuntu2.3 from
Ubuntu:18.04/bionic-proposed, I have not gotten any crashes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1743216
I installed xdg-utils 1.1.2-1ubuntu2.3 from Ubuntu:18.04/bionic-
proposed. We will see if it still crashes or not. Thank you Iain for
your work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-utils in Ubuntu.
Public bug reported:
Whenever as root in a terminal, I start 'gvim', the whole windows system
crashes and the user find himself on the gdm login screen. Windowing
session has been lost.
It only occurs with gvim. I tried xterm, terminator and gthumb as root
and these graphical application do not
Gnome bug #60280 (https://bugzilla.gnome.org/show_bug.cgi?id=60280)
reports:
António Fernandes 2018-01-02 18:50:55 UTC
Starting with version 3.28, nautilus will not handle the "files on desktop
background" feature. For better alternatives, read this blog post
Rolf, I would agree with you if bugs would be fixed in a timely manner,
but that is not the case. In the meantime, people go months if not
years with a scanner that does not work. That is unacceptable by any
standard. People should see my previous comment as a work around to get
things done.
After using the Nouveau driver for months, I needed performance and came
back to Nvidia proprietary driver 340.102 on Ubuntu 16.04. The problem
still exist, but my script that fix it by adding 'Option
"RegistryDwords" "EnableBrightnessControl=1"' into
I had a similar problem with the default version of gscan2pdf available from
the default Ubuntu 16.04 repositories. I would scan, but the error message
would arrive after the scan was completed.
gscan2pdf version 1.3.8.
I then installed the following PPA to get the latest version, 1.8.3:
What is odd is that it does not occur on all Ubuntu installations. I
have a 2nd Ubuntu machine that does not suffer from this issue. What
could possibly be different between a computer that exhibit this problem
and another? I do not recall having played with any configuration file
that relates
If network-manager 1.4.4 has fixed this issue, it then needs to be
backported to 16.04 LTS and 14.04 LTS.
--
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/1585863
Title:
WiFi
Éric Piel, add a sleep in that file and tell us if it fixes the problem
for you.
Something like:
post) $(sleep 10;/sbin/wpa_cli resume) & ;;
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
@Aron Xu, I can you be sure the problem is not Network Manager related?
I do not say you are wrong, but could you point to some evidence that
the Network Manager is not involved with this? Searching through the
comments, the word 'kernel' does not show often and none suggest that
the problem is
systemctl restart NetworkManager.service occasionally cause nm-applet to
crash. This occurs often when my laptop resumes because I have
installed a script that upon resume, restart the NetworkManager after a
3 seconds pause. This script has been added as a workaround because too
often, upon
Following is the stacktrace:
Stacktrace:
#0 0x7fd63e834a9a in g_slice_alloc () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#1 0x7fd63e834fce in g_slice_alloc0 () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2
@monte, I get the impression that you may suffer from more than one bug.
I have none of the symptoms you describe. I believe that this bug
report must remain focused on the resume issue. Any other issue should
be in another bug report (maybe already existing?).
In a sideline, sometimes I feel
And coming back to my workaround script
NetworkManagerRestartWorkaroundForBug1380480.sh, I tried the more
friendly '(sleep 3;sudo wpa_cli scan)' solution, but it dit not always
work. The only solution I found to have networking working reliably
after resume is to have NetworkManager restarted.
This serious issue is dragging to long. People want computers that
"just work". If pinpointing the source of the problem is difficult and
few resources are available, why not package a workaround that restarts
NetworkManager upon resume?
Attached is my workaround. Works nicely. Finally, I
This crucial bug that undermines the reputation of Ubuntu has remained
opened for a very long time. Obviously, the fix seams complicated since
it still has not arrived. But meantime, people want a working laptop,
period. This is the kind of bug that pushed many previous Linux users
to migrate
Guys, there are 117 users affected by this launchpad bug, but only 7
logged in upstream and CC themselves to the upstream bug. Please login
to the upstream bug at https://bugzilla.gnome.org/show_bug.cgi?id=703179
and CC yourselves. It might help to add importance to the issue.
--
You received
Bug# 1455097 "/etc/pm/sleep.d/ is no more processed" confirms that any
solution involving "/etc/pm/sleep.d/" will not work since systemd took
over. auspex solution works (thank you), although in my case, I simply
restart the Network Manager (systemctl restart network-manager) to be
really sure
It is not clear what this issue is really about. Is it about the
network-manager being frozen after resume?
This happens to me and the solution is to run:
sudo systemctl restart network-manager # >=16.04
or
sudo restart network-manager# <16.04
However, lauricat reports that this
Bug #1585863 is not the same, but until someone finds the proper fix for
both issues, why not introduce a script under /etc/pm/sleep.d that
restarts the network manager upon resume? Lets get something working
for the non technical people / consumer quickly. Such a script would
"solve" the
Bug #1380480 is not the same, but until someone finds the proper fix for
both issues, why not introduce a script under /etc/pm/sleep.d that
restarts the network manager upon resume? Lets get something working
for the non technical people / consumer quickly. Such a script would
"solve" the
Ubuntu (Unity) does not work perfectly. I have this problem using
Ubuntu 16.04 LTS Xenial Xerus with Unity.
--
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/1380480
Title:
Looks like this bug is a duplicate of Bug #1585863. But I will leave
experts in the matter to decide and declare the duplication, if any.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Looks like Bug #1448555 is a duplicate of this one.
--
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/1585863
Title:
WiFi malfunction after suspend & resume stress
Status in
Ok, so I upgraded my Lenovo w510 to Ubuntu 16.04 LTS Xenial Xerus and
the problem persists. The fix I provide works, though when changing the
brightness, it is jerky, i.e. it flashes between a low level and the
actual selected level. But once the desired level reached, all is good.
So, can we
You may follow Bug #1540110 which is the continuity of this bug, with
the upstream bug link.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/743927
Title:
SMART status is
rusty Tahr on 2016-01-26, gnome-disk-
utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.
This bug is the same as bug #1092900 which was reported against Ubuntu
10.04 LTS Lucid Lynx. Following user dino99 suggestion, I opened this
new bug report to follow the same problem
T data through a USB link. gnome-
disk-utility acknowledge SMART capabilities if the same disk is
connected through a SATA port.
Confirmed for Ubuntu 14.04 LTS Trusty Thar on 2016-01-26, gnome-disk-
utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.
This bug is the same a
confirming
that there is no problem reading SMART data through a USB link. gnome-
disk-utility acknowledge SMART capabilities if the same disk is
connected through a SATA port.
Confirmed for Ubuntu 14.04 LTS Trusty Thar on 2016-01-26, gnome-disk-
utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Ha
SATA port.
Confirmed for Ubuntu 14.04 LTS Trusty Thar on 2016-01-26, gnome-disk-
utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.
Original report -->
In terminal it wasnt enabled but it was supported.
I enabled it in 12.04 ubuntu in terminal.
In 10.04 in terminal
same disk is connected
through a SATA port.
Confirmed for Ubuntu 14.04 LTS Trusty Thar on 2016-01-26, gnome-disk-
utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.
Original report -->
In terminal it wasnt enabled but it was supported.
I enabled it in 12.04 ubunt
-01-26, gnome-disks-
+ utility 3.10.0, udisks 2.1.3 (built against 2.1.3) by Hans Deragon.
Original report -->
In terminal it wasnt enabled but it was supported.
I enabled it in 12.04 ubuntu in terminal.
In 10.04 in terminal it shows its enabled but see screenshot in Disk utility
dino99, does the version in 14.04 LTS has been corrected recently? I
have tried it on 14.04 on 2015-09-19, but not since then.
Can we reopen it against that version?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in
Current version of gnome-disk-utility in 14.04 is 3.10.0-1ubuntu3.
Searching through my history, i found that this package was never
updated, surely not since 2015-09-19 so the bug is still valid (I am not
home so I cannot try). Switching to 'confirm'.
** Changed in: gnome-disk-utility (Ubuntu)
@dino99. If it still affects 14.04, what should I do now? Recopy the
ticket? Or simply change the description?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1092900
This LTS Enablement Stack scares me a lot; I do not want to screw my
system. So if I understand you correctly, I should return to my
previous state with the following command, right?
sudo apt-get remove linux-generic-lts-vivid xserver-xorg-core-lts-vivid
xserver-xorg-lts-vivid
Any chances to have this bug backported to 14.04 LTS Trusty Thar?
Current version is 2.10.2.is.2.10.1-0ubuntu1.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1228567
Title:
M. Penalver, the link you provide does not indicate how to revert such a
change. I want to keep my OS LTS, not having it become obsolete in a
few months. Are you in contact with the people that created that link
and can you ask them to document the rollback procedure so I can return
to a pure
** Also affects: nvidia
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in Unity / Xorg
Following instructions found in bug #562005, I fixed the problem in
Ubuntu 14.04.03 LTS Trusty Thar. Attached, the script which fixes the
problem. It only creates the file /usr/share/X11/xorg.conf.d/99-nvidia-
proprietary-brigthness-keys-fix.conf if a card that suffers from the
problem is
Why is this bug report invalid? I still have the problem in 14.04.03
LTS. Who decides to change it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/562005
Title:
Thank you Ph-Hsu Lin for the clarification. Users who want to track
this issue with a new report, follow Bug #1389215.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu.
Problem still persist on 14.04.03 LTS (System fully updated as of this
writing). But this should be an option one can enable.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1282900
** Description changed:
+ gnome-disks (show as "Disks" on the desktop environment running Unity)
+ systematically does not acknowledge that disks have SMART capabilities
+ when connected through a USB port; SMART capabilities are grayed.
+ However, 'sudo smartctl -a /dev/' works fine.
Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=752121
** Bug watch added: GNOME Bug Tracker #752121
https://bugzilla.gnome.org/show_bug.cgi?id=752121
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 562005 ***
https://bugs.launchpad.net/bugs/562005
** This bug has been marked a duplicate of bug 562005
Backlight controls of laptops with NVIDIA NVS and Quadro FX 880M GPUs no
longer function while using proprietary drivers
--
You received this bug
Copying here my own observations about the problem, from my previous bug
report #1389215, now marked as a duplicate of this one.
---
Brightness controls are not working in Unity / Xorg. When pressing the
keys fnhome and fnend on my Lenovo W510, I see the indicator on
the screen showing the level
I tried acpi_backlight=vendor on grub to novail. It even stopped
working on the TTY. Putting grub as it was restored the functionality
back in the TTY. Under X11, the problem persists.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have this problem in Ubuntu 14.04 LTS Trusty Thar. I have a Lenovo
W510 laptop. Could it be that this problem occurs with only a certain
type of hardware? After all, not everybody using Ubuntu has this
problem.
My hardware is: 03:00.0 Network controller: Intel Corporation Centrino
@Sydney Dykstra (sydneyjd) , I do not believe you are having the same
problem. You should hunt for another ticket or create a new one.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
I replaced the official proprietary NVIDIA driver nvidia-331 with
nvidia-340 from xorg-edgers and the problem persists. nvidia-340
(340.76) is the latest driver for the legacy card Quadro FX 880M of my
Lenovo W510.
--
You received this bug notification because you are a member of Desktop
I fully understand that there are no resources to test this. Still, the
bug is valid and I cannot provide more input. It should be remained to
'new' to avoid expiration. It should not expire; it exist for real.
And having this bug open, someone else having the same problem might one
day stumble
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in Unity / Xorg because of
I do not have a spare drive, nor the time to perform such extensive
test. I am a desktop, power user and I cannot afford the time to do QA
on vivid. The problem still exist as of today on the LTS. Is anything
we can test on the LTS to get the fix on LTS?
--
You received this bug notification
Moved to 'new' to avoid expiration. I answered the question asked,
though I confirm that I cannot test with 15.04.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
Ah, I understand. No I cannot test it with the latest version of
Ubuntu. I do not have a spare computer to do so. However, it is still
relevant to Ubuntu 14.04 LTS Trusty Thar, which is a LTS and for which I
hope this bug will be fixed. Since I use Ubuntu as my main OS, I need
stability and
To avoid expiration of this bug, I put it back to 'new'. if more
information is required, please indicate in a comment what is required
and how to fetch that information.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member
Greetngs M. Penalver. I noticed that you have put back this bug in
Imcomplete with the additional tag needs-vivid-test. I fail to
understand what else I can provide you. What does needs-vivid-test
mean and how can I perform that test on my system? The problem still
exist, is real and should
The problem still persist on my laptop running Ubuntu 14.04 LTS Trusty
Thar, all packages updated up to 2015-02-25.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327208/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327213/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327212/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327215/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327204/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327205/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327198/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327203/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327200/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327199/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327214/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: nvidia-installer.log.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327217/+files/nvidia-installer.log.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Tags added: apport-collected possible-manual-nvidia-install
** Description changed:
Brightness controls are not working in Unity / Xorg. When pressing the
keys fnhome and fnend on my Lenovo W510, I see the indicator on
the screen showing the level of brightness
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327193/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327196/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327209/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327211/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327219/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: xserver.devices.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327220/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327194/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: NvidiaBugReportLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327206/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327201/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327202/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: DkmsStatus.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327197/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327195/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327210/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327216/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in Unity / Xorg because of
apport information
** Attachment added: nvidia-settings.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327218/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1389215/+attachment/4327207/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
There is no way to setup gpg-agent.conf:default-cache-ttl via GUI. I
believe that seahorse is the place where this option should show up.
In previous version of Ubuntu, there was a way to set it up with a GUI,
but I do not remember where anymore. I believe it was seahorse.
Upstream, a developer pointed to the following blog explaining the
current situation with Bluetooth and Gnome.
http://www.hadess.net/2011/11/obexftp-in-gnome-non-update.html
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in
1 - 100 of 128 matches
Mail list logo
