[Bug 1873641] Re: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.

2020-05-19 Thread Antti Palsola 
I got the sound working after trying the following fixes stated in 
:
- sudo alsa force-reload
- sudo apt install pavucontrol
- sudo apt install alsa-tools-gui and setting jack_detect = no
- timidity-daemon was already not installed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873641

Title:
  pulseaudio says: ALSA woke us up to write new data to the device, but
  there was actually nothing to write.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873641/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1873641] Re: pulseaudio says: ALSA woke us up to write new data to the device, but there was actually nothing to write.

2020-05-19 Thread Antti Palsola 
This happens also to me with my M-Audio Fast Track Ultra (yes, I know it
is an old device but it has worked until now) after upgrading from
Ubuntu 19.10 to 20.04 LTS. (Did not have any issues with 19.10.) My
motherboard is Asus Prime X570-P AM4.

$ systemctl status --user pulseaudio.service
● pulseaudio.service - Sound Service
 Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Tue 2020-05-19 13:27:58 EEST; 17min ago
TriggeredBy: ● pulseaudio.socket
   Main PID: 2209 (pulseaudio)
 CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
 └─2209 /usr/bin/pulseaudio --daemonize=no --log-target=journal

May 19 13:27:54 [HOSTNAME MASKED] systemd[2202]: Starting Sound Service...
May 19 13:27:58 [HOSTNAME MASKED] systemd[2202]: Started Sound Service.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write 
new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug 
in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA 
developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with 
POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value 
< min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA

Excerpts from /var/log/syslog:
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: ALSA woke us up to write 
new data to the device, but there was actually nothing to write.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: Most likely this is a bug 
in the ALSA driver 'snd_usb_audio'. Please report this issue to the ALSA 
developers.
May 19 13:28:10 [HOSTNAME MASKED] pulseaudio[2209]: We were woken up with 
POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value 
< min_avail.
May 19 13:28:23 [HOSTNAME MASKED] pulseaudio[2209]: GetManagedObjects() failed: 
org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes 
include: the remote application did not send a reply, the message bus security 
policy blocked the reply, the reply timeout expired, or the network connection 
was broken.
May 19 13:29:27 [HOSTNAME MASKED] pulseaudio[2209]: Got POLLNVAL from ALSA
 [Power off – power on cycle on M-Audio Fast Track Ultra] 
May 19 13:29:27 [HOSTNAME MASKED] kernel: [  194.584035] usb 3-3: USB 
disconnect, device number 2
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.207250] usb 3-3: new 
high-speed USB device number 5 using xhci_hcd
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.233340] usb 3-3: config 1 
interface 3 altsetting 0 bulk endpoint 0x7 has invalid maxpacket 8
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.233343] usb 3-3: config 1 
interface 3 altsetting 0 bulk endpoint 0x87 has invalid maxpacket 8
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234455] usb 3-3: New USB 
device found, idVendor=0763, idProduct=2080, bcdDevice= 1.51
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234457] usb 3-3: New USB 
device strings: Mfr=1, Product=2, SerialNumber=0
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234458] usb 3-3: Product: Fast 
Track Ultra
May 19 13:29:30 [HOSTNAME MASKED] kernel: [  197.234459] usb 3-3: Manufacturer: 
M-Audio
May 19 13:29:30 [HOSTNAME MASKED] mtp-probe: checking bus 3, device 5: 
"/sys/devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:05:00.3/usb3/3-3"
May 19 13:29:30 [HOSTNAME MASKED] mtp-probe: bus: 3, device: 5 was not an MTP 
device
May 19 13:29:30 [HOSTNAME MASKED] systemd[2202]: Reached target Sound Card.
May 19 13:29:30 [HOSTNAME MASKED] systemd[1385]: Reached target Sound Card.
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.083958] usb 3-3: set quirks 
for FTU Effect Feedback/Volume
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.098203] usb 3-3: set quirk for 
FTU Effect Duration
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.099701] usb 3-3: set quirks 
for FTU Effect Feedback/Volume
May 19 13:29:32 [HOSTNAME MASKED] mtp-probe: checking bus 3, device 5: 
"/sys/devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:05:00.3/usb3/3-3"
May 19 13:29:32 [HOSTNAME MASKED] mtp-probe: bus: 3, device: 5 was not an MTP 
device
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.489446] usb 3-3: Unable to 
change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.490200] usb 3-3: Unable to 
change format on ep #81: already in use
May 19 13:29:32 [HOSTNAME MASKED] kernel: [  199.490973] usb 3-3: Unable to 
change format on ep #81: already in use
May 19

[Bug 1877792] Re: jmespath SyntaxWarning: "is" with a literal.

2020-05-13 Thread Antti Palsola 
I confirm this. Running any Ansible playbook displays the following
warning on every task which is quite annoying:

/usr/lib/python3/dist-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with 
a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib/python3/dist-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with 
a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib/python3/dist-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with 
a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib/python3/dist-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with 
a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib/python3/dist-packages/jmespath/visitor.py:260: SyntaxWarning: "is" 
with a literal. Did you mean "=="?
  if original_result is 0:

The system is Ubuntu 20.04 LTS on amd64.

$ apt-cache policy ansible python3-jmespath 
ansible:
  Installed: 2.9.6+dfsg-1
  Candidate: 2.9.6+dfsg-1
  Version table:
 *** 2.9.6+dfsg-1 500
500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com 
focal/universe amd64 Packages
500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com 
focal/universe i386 Packages
100 /var/lib/dpkg/status
python3-jmespath:
  Installed: 0.9.4-2
  Candidate: 0.9.4-2
  Version table:
 *** 0.9.4-2 500
500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com focal/main 
amd64 Packages
500 http://www.nic.funet.fi/pub/mirrors/archive.ubuntu.com focal/main 
i386 Packages
100 /var/lib/dpkg/status

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877792

Title:
  jmespath SyntaxWarning: "is" with a literal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1877792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813672] Re: 4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked

2019-01-29 Thread Antti Palsola 
I have a similar issue with Lenovo ThinkPad X1 Carbon 20HR-002RMX,
Lenovo ThinkPad Thunderbolt 3 Dock 40AC0135EU and linux-
image-4.15.0-44-generic: The screen(s) go blank on the login screen (at
the latest).

No issues with linux-image-4.15.0-43-generic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813672

Title:
  4.15.0-44-generic #47 breaks Lenovo T470s suspend while docked

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813672/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1730039] Re: 389-console fails to connect with TLSv1.2

2018-06-11 Thread Antti Palsola 
This is also happening to me with Ubuntu 18.04 (bionic):

$ 389-console -D 9 -x nologo -u "cn=directory manager" -a 
https://:9830
 [clip] 
CommManager> New CommRecord (https://:9830/admin-serv/authenticate)
ResourceSet: found in cache 
loader501263526:com.netscape.management.client.theme.theme
ResourceSet: NOT found in cache 
loader501263526:com.netscape.management.client.comm.HttpsChannel
CREATE JSS SSLSocket
Unable to create ssl socket
org.mozilla.jss.ssl.SSLSocketException: SSL_VersionRangeSetDefault() for 
variant=0 with min=768 max=770 out of range (769:772): 0: (0) Unknown error
at org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefault(Native 
Method)
at 
org.mozilla.jss.ssl.SSLSocket.setSSLVersionRangeDefault(SSLSocket.java:1398)
at com.netscape.management.client.comm.HttpsChannel.open(Unknown Source)
at com.netscape.management.client.comm.CommManager.send(Unknown Source)
at com.netscape.management.client.comm.HttpManager.get(Unknown Source)
at com.netscape.management.client.console.Console.invoke_task(Unknown 
Source)
at 
com.netscape.management.client.console.Console.authenticate_user(Unknown Source)
at com.netscape.management.client.console.Console.(Unknown Source)
at com.netscape.management.client.console.Console.main(Unknown Source)
 [clip] 

389-console does not even try to connect to the server. (I verified that
with Wireshark.)

** 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/1730039

Title:
  389-console fails to connect with TLSv1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jss/+bug/1730039/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1010104] Re: org element is not handled correctly

2012-08-19 Thread Antti Palsola 
I don't know if this is a bug or a feature, but the 'ORG' entry seems to
take a list value. I. e. try:

v.add(org).value = [TEST]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010104

Title:
  org element is not handled correctly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-vobject/+bug/1010104/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs