Additional error messages from starting audaciuos with radio stream.
cliff@Desktopps:~$ audacious http://stream.srg-ssr.ch/rsc_fr/mp3_128.m3u
Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme
Gdk-Message: 09:09:07.328: Unable to load col-resize from the cursor theme
Switching to VLC to play the same radio stream works as expected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2052307
Title:
ALSA error: snd_pcm_open failed:
Public bug reported:
Getting the following error trying to play a radio stream in Audacious.
ERROR ../src/libaudgui/util.cc:328 [audgui_simple_message]: ALSA error:
snd_pcm_open failed: Operation not supported.
This occurred after the daily update on 2/2/24.
ProblemType: Bug
DistroRelease:
Unsure of librest update is installed correctly since I've never
installed a package this way. The following dpkg -l shows the librest
at 0.9.1.-2.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
cliff@cliffps:/etc/apt/sources.list.d$ dpkg -l | grep librest
ii librest-1.0-0:amd64
Public bug reported:
Crash occurred during apt upgrade.
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: pulseaudio-utils 1:14.2-2ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21
Uname: Linux 5.11.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Public bug reported:
Both my desktop and laptop running 20.10 have a 90 second delay shutting
down (power off or restart). Getting message;
A stop job is Running for Make remote CUPS printers available locally
After 90 seconds the shutdown continues to completion.
ProblemType: Bug
My resync is working fine again. Thanks for your attention to this bug-
report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1888685
Title:
rsync fails after installing
Appears to me is that failure criteria is if the directory being
rsync'ed is off of my home it will fail. Hard to believe I'm the only
one seeing this. Again this 20.10 system was functioning normally until
7/18 when 3.2.1 was installed.
--
You received this bug notification because you are a
Have a /etc/rsyncd.conf that moves data from path = /mnt/testrsync
directory on my desktop to my laptop and it works. Changing the
/etc/rsyncd.conf to path = /home/cliff/Bin fails with a chroot failure
(unable to find the path). Copied the /mnt to my home directory (cp -r
/mnt ./) so the only
No differences between /home/cliff/Bin and /mnt/testrsync (0755) both
owned by cliff:cliff. In building my test cast wanted to duplicated the
target directories as much as I could.
No I use the systemctl start/stop rsync so the answer is the daemon is
running under root.
--
You received this
This doesn't seem right to me. Changed the path = Bin and the call to
rsync to use the -R option which I think is to use relative path. Still
fails on chroot but the rsyncd.log has the following;
2020/07/29 08:52:17 [10277] rsync allowed access on module Bin_dir from UNKNOWN
(192.168.1.159)
Stumped to what to do next. Have two test cases, one works, one fails
with chroot error. Here is the rsyncd.conf that workds;
cat << EOF > /etc/rsyncd.conf
log file = /var/log/rsyncd.log
pid file = /var/run/rsyncd.pid
lock file = /var/run/rsync.lock
[test_dir]
path = /mnt/testrsync
comment =
Couldn't figure out how to make your example run on my 20.10 (or even
20.04) server systems. Using your example took apart my server/client
and made a simple case (using the /mnt/synctest directories) which runs
when the server is either 20.04 or 20.10. Will start looking at what to
add to make
Don't understand the server question. The syncd is enabled and started
at boot with the rsyncd.conf in /etc, rsyncd.srct in /etc and rsync in
/etc/default. The client start the rsync process with a cron job with
the attached script.
** Attachment added: "Resync.sh"
Christian, had this sync setup over many releases of Ubuntu without
issue. Have the syncd running on 20.10 and the client on 20.04. After
the install of 20.10 sync ran OK until the 3.2.1 level was installed.
Added the current syncd.conf (haven't made changes to this file for
several releases of
Public bug reported:
After installation of rsync.3.2.1 my attempt to sync fails with chroot
error. The rsyncd.log indicates that rsync can't find the directories I
want to sync.
2020/07/18 10:01:20 [3689] rsyncd version 3.2.1 starting, listening on port 873
2020/07/18 11:00:01 [5786] name
Public bug reported:
Install recent version of 19.10 daily build. All is well but can't set
a static route for my wired ethernet. Going to Settings-Network-Wired
tried to fill in IP Address/NetMask/Route and although all appears to be
correct the Apply button is never activated to set the
Don't recall seeing this problem on any subsequent releases of Ubuntu.
Now running 18.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1354596
Title:
Internal Server Error
This is no longer a problem in my environment. Don't recall which
release or update fixed it. Now running 18.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/780782
Title:
Reviewed all the available syslogs and found 2-3 of the apport-gtk
failures per day from 9/22 to 9/27. Only one failure on 9/28 and none on
9/29. Had other problems on 9/30 which required a re-install at the
9/29 build level. Will add a comment if this problem reappears.
--
You received this
Attaching the syslog text showing the sigfault and I think the
corresponding crash file.
** Attachment added: "_usr_share_apport_apport-gtk.0.crash"
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+attachment/4958871/+files/_usr_share_apport_apport-gtk.0.crash
--
You received
Both of these are installed
python-cffi-backend is already the newest version (1.9.1-2build2).
python-cffi-backend set to manually installed.
python3-cffi-backend is already the newest version (1.9.1-2build2).
python3-cffi-backend set to manually installed.
--
You received this bug notification
Unable to run apport-retrace. Get the following
cliff@cliffps:~/tmp$ apport-retrace _usr_share_apport_apport-gtk.0.crash
ERROR: report file does not contain one of the required fields: Package
First part of the crash file
ProblemType: Crash
Architecture: amd64
Date: Fri Sep 22 05:36:27 2017
This error has shown up in last week or so. Been running Artful for
over a month. Usually on every boot will open a command shell and
update/upgrade for the latest updates then open chrome. By then the
popup box shows up indicating the an error had occurred and asking if it
should be reported.
Public bug reported:
Daily notification of system error and request to report it but nothing
get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us
usually no crash dump generated.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apport 2.20.7-0ubuntu1
ProcVersionSignature:
Running 16.10 Gnome and regularly suspend the laptop. The background
picture turns into random rectangles on a black ground. No other
problems noticed. Restoring the same picture via right-click on the
desktop work until the next suspend.
--
You received this bug notification because you are
Don't think I can reproduce this error. At the time I could not boot
14.10 normally (upstart) and systemd would boot to a valid desktop but
missing some critical components (cups). I can now boot normally using
upstart but systemd fails to boot at all. Tried twice and booted to a
terminal
Now able to boot to a good Unity desktop. Installed unity-tweak-tool
and ran unity-tweak-tool --reset-unity. It hung in a wait condition and
would not complete. Decided to reboot and re-run the unity reset to
document the hang condition. The boot completed to a good desktop
(Unity launch bar
I went back and put the 14.04 level modules from xserver-xorg-video-
intel back onto the Unity 14.10 system. There was no difference, still
no Unity launcher or Ubuntu banner.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Rebuild the 14.10 Unity system using the Final Beta and continue to have
the problem of a desktop with no Unity launch bar or Ubuntu banner (top
line). The Gnome boot problem has been resolved, the correction did not
effect the Unity boot problem.
--
You received this bug notification because
Booted the Unity load, desktop opened with no Unity Launch bar and no
Ubuntu banner. Opened an xterm and ran the unity_support_test, output
below. Attaching the unity7.log associated with this boot.
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI
** Attachment added: /var/log/dmsg.log
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1363421/+attachment/4216715/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
Looked at the description of 1357746 which indicates problem caused by
the latest level of xserver-xorg-video-intel. The boot hang on black
screen forum entry (see Ubuntu Development Version) I had with Gnome
also involved the same component. In trying to debug the Gnome failure
it was
Saw some comment on the development forum that nomodeset corrected a
similar problem. This parameter does not correct on my system. Adding
some additional information, anything else needed?
** Attachment added: lshw from the failing system
Adding Xorg.0.log
** Attachment added: Xorg log
https://bugs.launchpad.net/unity/+bug/1363421/+attachment/4193261/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
Public bug reported:
Been having problems getting any 14.10 build (Gnome and Unity) to boot
on this desktop. Submitting problem report on Unity since seems easist
to document. I downloaded the Ubuntu 14.10 daily build dated 8/29/14
and went through the install process without any problem.
Public bug reported:
This is one of two problems I'm seeing on the Gnome version of 14.10.
Since there is a boot problem using the normal process (the first
problem) I've boot systemd with init=/lib/systemd/systemd rather than
using normal upstart boot. The system comes up but trying to open the
37 matches
Mail list logo
