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
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 Ubuntu
Touch
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 Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
This bug occurs often, 2 or 3 times per week.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to perl in Ubuntu.
https://bugs.launchpad.net/bugs/1758498
Title:
perl crashed with SIGABRT in _dbus_abort()
Status in perl
The link to the duplicate bug does not exists anymore. It was
https://bugs.launchpad.net/bugs/1761784. I removed the link so this bug
can be worked on.
** This bug is no longer a duplicate of private bug 1761784
--
You received this bug notification because you are a member of Ubuntu
Touch
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
ChristianEhrhardt (paelzer) and John Johansen (jjohansen), I tried your
sha1sum checks and all looks good, but the problem still persists.
Nothing suggested in this bug reports works for me. Luckily, on my
system where it fails, I do not make use of libvirt; this issue is just
an annoying error
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863
É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 Ubuntu
Touch seeded 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
@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
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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1380480
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1585863
Title:
WiFi malfunction after suspend & resume stress
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
Shouldn't this bug be assigned to some LXC/LXD task? After all, a
normal installation of the distributions on a computer works well.
16.04 shutsdown properly on a laptop, for example; systemd simply does
not hang. Thus this bug is somewhat related to LXC/LXD. Maybe the bare
minimum images are
Looks like it is the same problem.
** Attachment added: "ubuntu-xenialxerus-16.04-journal.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1519499/+attachment/4660855/+files/ubuntu-xenialxerus-16.04-journal.txt
--
You received this bug notification because you are a member of
I too cannot stop a container, but it is running Ubuntu Xenial Xerus
16.04 LTS. I cannot tell if the root cause is the same as reported by
this bug report though; I am not familiar with systemd.
I created a few days ago a new container on an updated Ubuntu Trusty
Thar 14.04 LTS host using the
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 Ubuntu
Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/1228567
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in
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
*** 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
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 Ubuntu
Touch seeded packages, which is
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 Ubuntu
Touch seeded 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 Ubuntu
Touch
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in Unity /
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 Ubuntu
Touch seeded packages, which is subscribed to
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
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
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: 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Changed in: xorg (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not working in Unity /
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded 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 Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Persists in Ubuntu 14.04 LTS Trusty Thar.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1010189
Title:
Characters are no longer hilited when searching
Status in
At a high level, I have the same problem: Network Mnager does not work
anymore after resume, about half the time.
My work around is to run in a terminal: sudo restart network-manager
As a side effect, nm-applet sometimes crashes when I do that. But it
works.
At a lower level, I am not sure
Still present in Ubuntu 14.04 LTS Trusty Thar. It used to be
configurable IIRC. Why the regression?
Workaround:
Edit ${HOME}/.gnupg/gpg-agent.conf
Add:
default-cache-ttl 86400 # default-cache-ttl in secondes, here
representing 24 hours.
Logout for this to take effect.
--
You received this
Thank you Mr Murray to assign a package to the problem. But I am
curious how you came about it as 'indicator-network' does not show up in
my list of running processes. I just want to be sure that the bug is
assigned to the right package.
# ps -e --format args | fgrep indicator
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
** This bug is no longer a duplicate of bug 830348
desktop contents briefly visible on resume from suspend before lock dialog
** This bug has been marked a duplicate of bug 1280300
Desktop contents
Discovered another behaviour. If you play with the brightness controls
under Xorg, nothing changes. However, suspend the computer and resume
it, and the brightness will be setup to the last setup you left when
playing with the brightness controls. Thus, the value in the kernel
persists.
You
Found out that brightness control works fine with Nouveau driver, but
not with Nvidia proprietary driver.
** Summary changed:
- Brightness controls are not working in Unity / Xorg.
+ Brightness controls are not working in Unity / Xorg because of Nvidia
proprietary driver.
--
You received this
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1389215
Title:
Brightness controls are not
Some more clarification. I tried under KDE Plasma 5.1 (Neon) and still
I could not change the brightness of the backlight.
However, the CLI commands that fail in a terminal running under an Xorg
session work flawlessly under a console (CTRLALTF1).
cd /sys/class/backlight/acpi_video0
echo 5
Same problem. Both host and guest are running Ubuntu 14.04 LTS Trusty
Tahr. Switching to 'vga' video card works, but rendering is slower.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
Public bug reported:
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 changing, so key mapping is
not the problem. However, the brightness is not changing.
On the
84 matches
Mail list logo
