Public bug reported:
At startup on Xubuntu after software update in VirtualBox.
ProblemType: Crash
Date: Thu Mar 1 19:37:48 2012
ExecutablePath: /usr/bin/blueman-applet
ExecutableTimestamp: 1317206831
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/blueman-applet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944467
Title:
blueman-applet crashed with DBusException in call_blocking():
org.freedesktop.DBus.Error.ServiceUnknown: The name :1.69 was not
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/944466
Title:
oneconf-query crashed with ImportError in /usr/lib/python2.7/dist-
packages/oneconf/packagesethandler.py: No module named distributor
Public bug reported:
At boot time Xubuntu after a few upgrades (apologies, I dont know what
changed).
ProblemType: Crash
CrashCounter: 1
Date: Thu Mar 1 19:24:28 2012
ExecutablePath: /usr/share/oneconf/oneconf-query
ExecutableTimestamp: 1329523645
InterpreterPath: /usr/bin/python2.7
*** This bug is a duplicate of bug 440889 ***
https://bugs.launchpad.net/bugs/440889
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/919557
Title:
@Karl Ryder: FTR, I just yesterday followed the steps at
https://wiki.ubuntu.com/KernelTeam/MainlineBuilds to install the kernel
at http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2010-05-06-lucid/
. It fixed the USB suspend problem and it didn't cause many other
problems. I think it might
This bug still exists in Lucid.
--
Shouldn't look up python in path
https://bugs.launchpad.net/bugs/328657
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http://packages.ubuntu.com/trusty/pepperflashplugin-nonfree also works
for me on amd64 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311237
Title:
Pepper Flash needs backport to 12.04
To
Similar output of ccid conformance as James' from a few years back.
** Attachment added: "output of src/parse from ccid-1.4.26"
https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1307109/+attachment/4821262/+files/output.txt
--
You received this bug notification because you are a
I'll also note that the A22CR card works fine (does not exhibit the
flapping behavior) in an external Feitian reader.
Interestingly, the A22CR card + Alcor combibation doesn't "flap" under
Windows either when running opensc-tool in a loop. Just under Linux.
--
You received this bug
I have the same problem, using pcscd 1.8.14-1ubuntu1.16.04.1 on an IBM
Thinkpad P50, which has the same card reader.
However, interestingly, it only happens when I use a Feitian/Entersafe
A22CR card. I tried two of them with the same result, so it's not a
flaky card either.
When I use a PIVKey
Identical issue, Ubuntu 16.04, Thinkpad P50 (Quadro M2000M in Discrete
mode) using nvidia-367 version 367.57-0ubuntu0.16.04.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292830
Title:
Resuming
I've just found that the same issue does not seem to happen if I resume
from sleep without my external monitor connected via DisplayPort.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1292830
Title:
Another data point: an Aventra MyEID PKI card
(http://www.aventra.fi/webshop/index.php?route=product/product_id=53
; it's apparently a "version 4", on the invoice it's identified as SKU:
MYEID and MPN: TH#130) works fine in this Alcor reader under OpenSC on
Ubuntu. The only card that has this
I had ipv6 disabled on my network interface. Reenabling it allowed
redis to start up fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752207
Title:
package redis-server 5:4.0.8-2 failed to
After having the same problem, I dist-upgraded to proposed and can
confirm that it fixed it (I did an apt-get purge nividia* before the
dist-upgrade then a apt-get install nvidia-384 after the dist-upgrade)/
One thing that this minor bug pointed out to me is that it has become
inconvenient in the
** Attachment added: "output of strings against steam's internal dump format"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752468/+attachment/5065699/+files/steamdump
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
A dialog with glxChooseVisual failed is put up when the steam launcher
attempts to execute the steam client after an update to nvidia-390
today.
Here is the output of "strings /tmp/dumps/assert_20180228205801_6.dmp"
(attached)
** Affects: nvidia-graphics-drivers-390
The symptoms remain after a "apt purge steam && rm -rf
/home/chrism/.steam && apt autoremove && apt install steam".
I neglected to mention that I am on "proposed" repo; my system is
current with that repo as of now.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Additonal notes because I know a similar symptom like the one I describe
in #1 can be caused by multiple issues.
- my system display BIOS is in Hybrid mode, and PRIME Settings do show
up in an Ubuntu 16.04 install I have on the same system.
- the selected driver is NVIDIA in Software and Updates
I can confirm the results of xrandr and dmesg|grep drm above with the
same kernel and nvidia driver versions on my system (a Thinkpad P50 with
an M2000M).
An additional symptom I have is that the nvidia-settings application no
longer supports PRIME at all; the PRIME Settings category in the
Thanks for the confirmation, Doug! I'll read up on libglvnd to feel
less clueless.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752739
Title:
PRIME Synchronization doesn't work with linux-kernel
Public bug reported:
When you are in the initial install state, you can easily switch from
the Nouvea drivers to the Nvidia drivers by choosing the option in
"Software and Updates -> Additional Drivers". However, when you attempt
to switch back (by selecting the nouveau option and clicking
Given that even a PRIME switch requires a logout and a reboot isn't that much
worse,
I think it's a reasonable workaround for initial release (not far away, and
reading about the current state of affairs, probably too imminent to get PRIME
working again) to require that folks switch drivers to
The rationale about why this is a probably an important bug to fix:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1752739/comments/5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This appears to be fixed in the deps of the current repo iteration of
the nvidia-driver-390 package (390.25-0ubuntu4); or at least Steam works
after a purge and reinstall that package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Burt P wrt https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1752053/comments/43, you might try this:
edit /etc/default/grub, editing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to:
GRUB_CMDLINE_LINUX_DEFAULT=""
And adding:
GRUB_GFXMODE=1920x1080-32,auto
Downgraded from proposed using pins and after a dist-upgrade it works,
thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot graphical display
To manage
More info:
```
chrism ~ ls /var/run/redis/
chrism ~ sudo systemctl start redis
Job for redis-server.service failed because a timeout was exceeded.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
chrism ~ journalctl -xe
-- The result is RESULT.
Feb 27
Public bug reported:
After apt-get dist-upgrade tonight on bionic.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: redis-server 5:4.0.8-2
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Moar:
```
root@bionictest:/var/log/redis# tail redis-server.log
30526:C 27 Feb 20:18:40.937 # Configuration loaded
30527:M 27 Feb 20:18:40.938 # Creating Server TCP listening socket ::1:6379:
bind: Cannot assign requested address
30868:C 27 Feb 20:20:11.428 # oO0OoO0OoO0Oo Redis is starting
For the record, I have a Lenovo P50 running Ubuntu MATE (which uses
lightdm), also in am Ultradock. It is running in "Discrete" (NVIDIA)
mode using nvidia-396 from the graphics-driver ppa, and had been working
well since at least -34.
When I upgraded to -38 (from -36), the system comes up to the
I'm updated fully as of today under 20.04 and have the same issue
described in OP with an NVIDIA M2000M in a Thinkpad P50 using the
proprietary drivers and 1 1080p monitor (the laptop panel) and 1 4k
monitor (Dell external).
#83 indicated that they changed things so that their PRIME settings were
And apologies for the multicomment spam but the output of apt-cache
policy libmutter-6-0
libmutter-6-0:
Installed: 3.36.4-0ubuntu0.20.04.2
Candidate: 3.36.4-0ubuntu0.20.04.2
Version table:
*** 3.36.4-0ubuntu0.20.04.2 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main
Here's the output of `nvidia-smi`, FTR:
+-+
| NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: 10.2 |
|---+--+--+
| GPU Name
I should note that when I say "proprietary" above, I mean the nvidia-
driver-440 package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870736
Title:
[nvidia] Screen scaling 125% gives 200%
To
Not that it's worth much, but I will side with the folks who want to be
able to configure paths as exceptions to the hardcoded rule of "only
allow access to files in /dev, /etc, and /home" either globally or per-
snap. I cannot fathom a reason for a central authority to distrust a
local
This symptom is back in today's daily build of 22.04 when attempting to
install to ZFS/zsys with encryption. I was able to install to ZFS/zsys
without encryption successfully.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
38 matches
Mail list logo
