If someone learns about Klondike from a friend and wants to play, they
look for the Klondike game. Dismissing the bug and giving a lesson in
linguistics and how they might select "Canfield" if their computer
language is set to English (UK) is just plain weird.
This presents as a good case study in
Public bug reported:
Summary:
Executing a sudo (that does not require a password) in a /bin/bash script
leaves the terminal as though it is reading a password (-echo, -icrnl, -ixon,
-opost, -isig, -icanon, -iexten)
To recreate the problem: (See attached log)
In a fresh install of 22.04.1 (desk
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
New test result today seems to be a intel P-state related problem.
I had reverted everything to their default state, with only the following
changes in TLP settings:
/etc/default/tlp
# Set Intel P-state p
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I did a few more tests. On my system, the combination of a realtime
(lowlatency) kernel and certain tlp settings fixed the random crash.
Although the side effect was the machine can get very hot because CPU
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
If you were testing on a laptop without a power supply connected, there
is an additional TLP settings change:
SCHED_POWERSAVE_ON_BAT=0
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
On my system:
1) the problem doesn't seem to be related to i915 firmware (which the archlinux
report I mentioned)
2) the problem seems to be triggered by a spike in CPU/GPU stress, it can be
triggered by t
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Here is the crach log and further discussion linked by the bug reporter on
archlinux:
https://github.com/nisenbeck/ct-server-2016-jessie/issues/1
** Attachment added: "intel_crash.txt"
https://bugs.lau
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I have a machine with intel Skylake and it is suffering random reboot.
Although I'm not familiar with hardware side of things, please let me
know if there is anything I can help.
Meanwhile, the archlinux co
Public bug reported:
attempted to install cups from
https://help.ubuntu.com/lts/serverguide/cups.html using the teminal and ran
into error message:
Errors were encountered while processing:
/var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an
I upgraded to colord 1.2.12-1ubuntu1 from Xenial and this issue is
solved after that.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
Primary screen not lis
I dicovered that "sudo colormgr get-devices" listed my devices, while
"colormgr get-devices" does not. Is this a privilege issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bug
There is a terminal command:
colormgr get-devices
I wonder it list anything on 15.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
Primary screen not lis
I can confirm this bug from Ubuntu Gnome 15.10, after all newest
packages installed. This did not happened in 14.04.x and 15.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs
That's odd - the error had been annoying me every boot for months has
now gone, even after "apt-get --purge bluez-dbg; reboot" and then the
same for bluez-dbg. To be clear, the last time the error appeared was
at boot time before installing both bluez-dbg and libbluetooth3-dbg as
per comment #7.
I was looking at the details before letting apport submit the bug and I
noticed that the stack trace I was just like the one submitted here
having no debug information available. So I ran 'sudo apt-get install
bluez-dbg libbluetooth3-dbg', rebooted and the problem went away... it's
a hiesenbug. :
Public bug reported:
The computer randomly locks up. I switched to nouveau because NVIDIA
tested driver caused artifacts with SLI enabled. But nouveau doesn't
seem to support SLI and locks up randomly. See attached screenshot
about DRM GPU lockup.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
P
** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu)
Importance: Undecided
Status: New
** Package changed: nvidia-graphics-drivers-310-updates (Ubuntu) =>
nvidia-graphics-drivers (Ubuntu)
** Summary changed:
- Enabling SLI on NVIDIA "tested" drivers causes artifacts and freeze
** Also affects: xorg-server
Importance: Undecided
Status: New
** Project changed: xorg-server => nvidia-drivers-ubuntu
--
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
** Description changed:
If SLI is enabled, there are many flickering artifacts and double images
- (especially tooltips). Eventually, the desktop environment locks up
- completely and the computer needs a forced manual reset. I needed to
- disable SLI as soon as possible and restart in order t
** Attachment added: "Since bug doesn't show up in screenshot, I took a picture
of the monitor."
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1365102/+attachment/4194843/+files/20140903_183606_resized.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch s
Bug does not show up in screenshot which means ... ?
Bug is easy to reproduce. Use recommended NVIDIA driver with any two
NVIDIA cards in SLI and see bug right away.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ub
Public bug reported:
If SLI is enabled, there are many flickering artifacts and double images
(especially tooltips). Eventually, the desktop environment locks up
completely and the computer needs a forced manual reset. I needed to
disable SLI as soon as possible and restart in order to get out o
22 matches
Mail list logo
