The only way to get /etc/init.d/pcscd installed is to first purge the
pcscd package and then install it newly.
The installation process never asks whether or not to overwrite a modified
version of the file - neither in Synaptic nor with apt-get on command line
.
Even if I delete
Since this is my first fault report here I probably made the mistake to
assign it to pcsc-cyberjack instead to pcscd = trying to fix it right
now
** Package changed: pcsc-cyberjack (Ubuntu) = pcsc-lite (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can confirm this problem.
I could fix it by replacing my /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0
with the version libusb-1.0-0_1.0.9~rc3-2ubuntu1 (probably a newer version
would also work, I just could not
find one).
The version which did NOT work:
apt-cache policy libusb-1.0-0
Wow
I figured out that /etc/init.d/pcscd is simply not getting installed by
the package although it is contained in pcscd_1.8.10-1ubuntu1_amd64.deb.
This is why I still had an old version of it on my machine.
Since I am no package expert I just can guess that this happens because
it is not
Public bug reported:
/etc/init.d/pcscd * resp. service pcscd * works only at first start.
In all other cases it just does nothing resp. starts one more pcscd.
Examples:
root@liberty:/etc# service pcscd start
root@liberty:/etc# ps -ef|grep pcscd
root 3850 1884 0 16:09 pts/10 00:00:00
It seems that after unplugging one of the devices which are causing
problems the subsequent plugging of ANY USB device leads to a crash of
pcscd.
I checked this with two Smartcard Readers (Gemalto PC Twin Reader and
IDENTIV CLOUD 2700 F) which are both working perfectly fine, and one USB
flash
Public bug reported:
When changing print server settings:
gnome-control-center -> Devices -> Printers -> Additional Printer
Settings ... => system-config-printer.py is started -> Server Settings
-> PreserveJobHistory No
CUPS will automatically be restarted but does not come up any more
because
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1787875
Title:
system-config-printer.py empties cupsd.conf
To manage notifications about this bug go to:
Public bug reported:
After Logout or Resume one ultimately ends up at a black screen on a
completely unresponsive system.
Only the power button helps in this case - I guess the "Emergency Sync"
in the attached syslog marks the point in time when the power button was
pressed.
###
apt-cache
Done.
cat /var/lib/whoopsie/whoopsie-id
9308e09d7878d0c0d8ead53939cd5e88e7c149ecd35cb08a25e4baa94126f02dc10b574f67e99c30cfae4f2ee05852ce672611907b1c0d49afa3bf0a48bd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For a while Logout/Resume/Switch User worked fine with Wayland (as well
as with Xorg when I cross-checked it).
But finally, when I tried "Switch User" again with Wayland, I got stuck
on the Login-Page of the current user - it was not possible to get the
page displaying all available users.
To be
Hi!
The new installation led me to the source of the problem:
The password was stored in seahorse (aka "Passwords and Keys").
Sorry for any inconvenience caused :-|
On 17.09.19 10:06, Marc Deslauriers wrote:
> Hi! Can you reproduce this issue on a freshly installed Ubuntu?
>
> ** Changed in:
It is no fault.
My original FR concerned gpg-agent because I was unaware of the fact
that
seahorse/gnome-keyring had the password stored.
On 05.11.19 11:26, Sebastien Bacher wrote:
> Thank you for your bug report. Could you give details on what you did
> exactly? If you ticked the box to store
Thanks!
On 05.11.19 21:30, Sebastien Bacher wrote:
> thanks, closing then
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Incomplete => Invalid
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It works!
On 09.03.20 21:17, Sebastien Bacher wrote:
> COuld you test the upstream workaround and use
> GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
This works in Python 2:
mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
This does not work in Python 3:
mystore = Gtk.ListStore(int)
It should indeed be done like this:
import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk
from gi.repository import GObject
mystore = Gtk.ListStore(GObject.TYPE_UINT64)
mystore.insert_with_valuesv(-1, [1], [GObject.Value(GObject.TYPE_UINT64,
1330400507426)])
###
I
I'm not sure what exactly they are really talking about at
https://gitlab.gnome.org/GNOME/pygobject/issues/198.
My FR concerns 3.26.1-2ubuntu1 and at gitlab it is stated "I think it
used to work in 3.26." which
clearly is not the case.
I took a look into the source and in pygi-value.c I found
While it is possible to create a bootable Stick from an original Ubuntu
20.04 iso it does not work for a modified one - even though the
/.disk/info files are identical.
It even depends on the name of the source iso how Startup Disk Creator behaves.
If it does not contain "Ubuntu", the window in
Public bug reported:
Neither the prepend nor the append statement in /etc/dhcp/dhclient.conf
works anymore.
E.g.:
prepend domain-name-servers 1.1.1.1,8.8.8.8;
---
lsb_release -rd
Strangely usb-creator was shown instead of isc-dhcp.
** Package changed: usb-creator (Ubuntu) => isc-dhcp (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882797
Title:
prepend statement in
Correction:
On Bionic:
If it does contain "Ubuntu", the window in the end just contains one "Quit"
button.
This is also the case after creating a bootable Stick from an original Ubuntu
20.04 iso.
If it does not contain "Ubuntu", the window has two buttons - "Test
Disk" and "Quit".
On Focal:
This could have the same reason as the bug filed by me:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1882797
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845793
Title:
Since upgrade to
I have the same problem on my Acer.
Since Kernel 5.8.0-36 and also 5.8.0-38 Ubuntu 20.04.1 cannot start in graphics
mode.
(It is possible to log in on the console using e.g. Ctrl+Alt+F4 though.)
With Kernel 5.4.0-58 the system works as expected.
The problem occurs only on this system, which is
Maybe contains extra information.
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+attachment/5453569/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have these installed:
dpkg -l | grep "linux\-[a-z]*\-"
rc linux-modules-extra-5.4.0-42-generic 5.4.0-42.46
ii linux-modules-extra-5.4.0-58-generic 5.4.0-58.64
ii linux-modules-extra-5.8.0-36-generic 5.8.0-36.40~20.04.1
ii linux-modules-extra-5.8.0-38-generic
After having played around with "prime-select" instead of using the
graphical Nvidia tool my system now also boots in "on-demand" mode.
(You have to reboot after changing the settings with "prime-select".)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The problem persists with Kernel 5.8.0-50, but I found out that it only
occurs if the usage of the Nvidia GPU is set to "on-demand".
In pure Intel or Nvidia mode the system boots as expected.
The mode van be set via graphical Nvidia tool or via "prime-select
{nvidia|intel|on-demand|query}".
28 matches
Mail list logo
