I can confirm that the issue is still there in Ubuntu 18.04.4 LTS.
I'm not sure if it counts, but landscape-client is not installed on the
affected system.
Instead there is landscape-common installed. I tried to add the package to the
affected packages list of the bug, but without any success.
Workaround: $ sudo apt install python-gi
After installing python-gi the light-locker-settings starts without issues.
I think there is a missing dependency from package light-locker-settings to
python-gi.
Adding this dependency should fix this issue.
$ apt-cache policy light-locker-settings
I can confirm that for XUbuntu 18.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1661682
Title:
light-locker-settings has a missing dependency to python-gi
To manage notifications about this
It's the same on Ubuntu 18.04.
$ LANG=C apt-cache policy software-properties-gtk
software-properties-gtk:
Installed: 0.96.24.32.12
Candidate: 0.96.24.32.12
Version table:
*** 0.96.24.32.12 500
500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
500
Public bug reported:
What I expected to happen:
When exiting from virtual terminal I expected to get back to gnome session with
working keyboard and mouse.
What happened instead:
When exiting from virtual terminal I was switched automatically back to
(locked) gnome session and keyboard and
Public bug reported:
On Zotac ZBOX NANO AQ01 remote control with in build ir receiver does
not work.
$ irw # gives not output at all
$ mode2 -d /dev/lirc0 # gives output
$ sudo dpkg-reconfigure lirc # Windows Media Center Transceivers/Remotes (all)
chosen
$ sudo systemctl status lirc
●
I can confirm the issue on Ubuntu 18.04 Server.
If there is a fixed upstream version, what is needed to see an updated package
in Ubuntu?
Is there anything I can help with?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm the issue with freshly installed Ubuntu Server 18.04.
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
$ sudo apt-cache policy linux-image-4.15.0-33-generic
I've tried the workaround, and it worked for me as described. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788235
Title:
lirc broken on 18.04
To manage notifications about this bug go to:
I can confirm the issue on a recently fresh installed Ubuntu Server
18.04. The goal was to transform the installation to a HTPC running kodi
and tvheadend (hts). Here are some links to guys who had the same
experience and offer a workaround until the fix of the package.
Same experience:
I've reinstalled network-manager and commented out all lines associated
to eth0 in /etc/network/interfaces. Now whoopsie is able to see if the
system is connected to the inter net again. perhaps one "quick" solution
could be making the package network-manager a hard dependency for
whoopsie
Restarting networking does not bring whoopsie online.
$ sudo systemctl restart networking
$ sudo systemctl status whoopsie
● whoopsie.service - crash report submission daemon
Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor
preset: enabled)
Active: active (running)
Yes, mythbuntu.
$ lsb_release --all
LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:
Sure, let me know if you need more information.
$ journalctl -u whoopsie
-- Logs begin at Mi 2017-08-16 19:20:23 CEST, end at Mi 2017-08-16 20:49:31
CEST. --
Aug 16 19:20:29 obelix systemd[1]: Started crash report submission daemon.
Aug 16 19:20:29 obelix whoopsie[1332]: [19:20:29] Using lock
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1710995/+attachment/4933488/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1710995/+attachment/4933489/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710995
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1710995/+attachment/4933486/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Tags added: apport-collected autoreport-false
** Description changed:
Reporting crashes from /var/crash/* is not possible any more.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: whoopsie 0.2.52.5
ProcVersionSignature: Ubuntu
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1710995/+attachment/4933487/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think so. Curl gets the following answer.
$ curl https://daisy.ubuntu.com
Invalid BSON.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710995
Title:
whoopsie not online
To manage notifications
sjuk@obelix:/var/crash$ sudo systemctl status whoopsie
● whoopsie.service - crash report submission daemon
Loaded: loaded (/lib/systemd/system/whoopsie.service; enabled; vendor
preset: enabled)
Active: active (running) since Di 2017-08-15 23:58:15 CEST; 1h 9min ago
Main PID: 1327
Public bug reported:
Reporting crashes from /var/crash/* is not possible any more.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: whoopsie 0.2.52.5
ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm
Public bug reported:
Normally when initiating a restart mythtv (mythfrontend/mythwelcome)
shuts down the system fast and clean. But restarting (from mythfrontend)
the system needs several minutes to shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mythtv
Public bug reported:
On exit I normally expect kodi to close fast and clean.
But about every second time kodi hangs on exit and crashes with core and log.
It seems that it doesn't matter if I use any function of kodi. Because I tried
to start and exit kodi several times without playing any media
Public bug reported:
The following Shortcut-Keys does not work any more in ubuntu.
Description from "man xorg"
Ctrl+Alt+Keypad-Plus
Change video mode to next one specified in the configuration
file. This can be disabled with the DontZoom xorg.conf(5) file option.
Public bug reported:
Package nvidia-346 does not depend on linux-headers-generic.
But without linux-headers the nvidia kernel module does not start.
Description:Ubuntu 14.04.3 LTS
Release:14.04
nvidia-346:
Installiert: 346.96-0ubuntu0.0.1
Installationskandidat:
It affects me too (mythbuntu thrusty x64).
Description:Ubuntu 14.04.2 LTS
Release:14.04
anacron:
Installiert: 2.3-20ubuntu1
Installationskandidat: 2.3-20ubuntu1
Versionstabelle:
*** 2.3-20ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64
I fixed it with this script. I don't remember exactly where I found it.
But I think it was on the mythtv users mailing list.
#!/bin/bash
mask=16
mythshutdown --status
status=$?
while (($status $mask))
do
mythshutdown --unlock
mythshutdown --status
status=$?
done
--
The issue is still there in trusty (14.04). So I will use pidgin again
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179180
Title:
Impossible to open Empathy contact list window if already
package added
** Project changed: mythbuntu = mythtv (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1236657
Title:
tmdb3.py crashed with TMDBRequestInvalid in handle_status(): Invalid
id
Please perform a Stable Release Update...
[Impact]
* Boot time in 12.04 (LTS) takes 100 % longer than in 13.10
* LTS Release users will think ubuntu is slower than windows
[Test Case]
* activate bootchart, reboot and take a look in /var/lob/bootchart:
about 45 sec. is normal / about 90
Yes. I only upgrade to long term support release on productive machine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
upstart needs more than 100 seconds to start a desktop
To
Hello Christopher M. Penalver, I tested it with the latest development
release. System was up in about 45 seconds.
The 12.04 installation needs about 90 seconds to boot up (look at
bootchart in the attachment for details).
If there is something I can test. Only ask ;-)
** Attachment added:
See attached the rest of the the bootchart information...
** Attachment added: asterix-precise-20130905-1.tgz
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1004975/+attachment/3804008/+files/asterix-precise-20130905-1.tgz
--
You received this bug notification because you are a member
mythlogserver crashes on on frontend-mythbuntobox and on front-/backend-
mythbuntubox, and it does unpredictable. Perhaps there is some hint in
the mythfrontend.log (see attachment).
** Attachment added: mythfrontend.log
Public bug reported:
Description:Ubuntu 12.04.1 LTS
Release:12.04
mythtv-frontend:
Installiert: 2:0.25.2+fixes.20120802.46cab93-0ubuntu1
Kandidat:2:0.25.2+fixes.20120802.46cab93-0ubuntu1
Versionstabelle:
*** 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0
500
I tested with witch kernel v3.7-rc6. The problem persists and the boot
time increased to about 140 seconds.
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
upstart needs more than 100 seconds to
Public bug reported:
Description:Ubuntu 12.04.1 LTS
Release:12.04
mythtv-common:
Installiert: 2:0.25.2+fixes.20120802.46cab93-0ubuntu1
Kandidat:2:0.25.2+fixes.20120802.46cab93-0ubuntu1
Versionstabelle:
*** 2:0.25.2+fixes.20120802.46cab93-0ubuntu1 0
500
apport information
** Tags added: apport-collected running-unity
** Description changed:
When turning on my desktop I expect to wait from 25 to 30 seconds until
the login screen appears.
But I have to wait more than 100 seconds until the login screen appears
(look at the bootchart
apport information
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437717/+files/AlsaDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437718/+files/AplayDevices.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437719/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: Card0.Amixer.values.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437720/+files/Card0.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card0.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437721/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Amixer.values.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437722/+files/Card1.Amixer.values.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.0.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437723/+files/Card1.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.1.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437724/+files/Card1.Codecs.codec.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.3.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437726/+files/Card1.Codecs.codec.3.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: Card1.Codecs.codec.2.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437725/+files/Card1.Codecs.codec.2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437727/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437728/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437729/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
apport information
** Attachment added: PciMultimedia.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437730/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437731/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437732/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437733/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437734/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437736/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
apport information
** Attachment added: PulseList.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437735/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1004975/+attachment/3437737/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
I added the needed log-files by apport-collect 1004975 and changed the
status of the bug to Confirmed.
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug is still present in Brasero 3.4.1 on Ubuntu 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/474233
Title:
brasero does not eject disk after burning
To manage notifications about this
Public bug reported:
Description:Ubuntu 12.04.1 LTS
Release:12.04
brasero:
Installiert: 3.4.1-0ubuntu1
Kandidat:3.4.1-0ubuntu1
Versionstabelle:
*** 3.4.1-0ubuntu1 0
500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 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/1048167
Title:
brasero does not eject disk after burning
To manage notifications about this bug go to:
I do not know what the meaning of LMDE is.
But sure is that one mencoder instruction fails with 64 bit package
while 32 bit package does a good job.
What can I do to get closer to the origin of the failure
(mencoder/mplayer or some libs?!?).
what should I test?
--
You received this bug
Thanks to thomlark, who delivered the proof that there is a problem with
the 64-bit mencoder.
Is there any one who can fix it?
I can test the fixed package.
Let me know i I should test something...
** Changed in: medibuntu
Status: Incomplete = Confirmed
** Changed in: mplayer (Ubuntu)
I use divxenc as frontend. Here is what it writes into it's batchfile.
#!/bin/bash
# Automatically generated by divxenc 1.6.4 on So 3. Jun 17:45:10 CEST 2012
### START OF COMMANDS ###
test -d /home/sjuk || mkdir -p /home/sjuk
test -d /home/sjuk/.divxenc/job15834
I can confirm. And it's the same with the ubuntu mencoder-/mplayer-
package on 64-bit.
** Also affects: mplayer (Ubuntu)
Importance: Undecided
Status: New
** Changed in: medibuntu
Status: New = Confirmed
** Changed in: mplayer (Ubuntu)
Status: New = Confirmed
--
You
Public bug reported:
While watching tv video freezes and falls back to main menu.
I'm using a combination of front- and backend on one mythbuntu-box.
Here you can see what mythfrontend wrote to its logfile:
May 27 15:32:58 obelix mythfrontend[2860]: W Decoder ringbuffer.cpp:1022
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005224
Title:
Video frame buffering failed too many times
To manage notifications about this bug go to:
I can confirm
$ sudo zcat cups.log.*
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer
configuration
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer
configuration
cupsd failed to create /var/run/cups/cups.sock, skipping automatic printer
Public bug reported:
The problem:
When klicking in gnome-control-center sound - test sound on button test
I expect to here any sound,
or at least a visual feedback that there was playing a sound.
Instead of that I get nothing of the expected. Klicking on the button
leads to nothing :-(
The
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004973
Title:
test sound in gnome-control-center does not work
To manage notifications about this bug go to:
Public bug reported:
When turning on my desktop I expect to wait from 25 to 30 seconds until
the login screen appears.
But I have to wait more than 100 seconds until the login screen appears
(look at the bootchart attachment).
Is there any I can do to improve the boot time?
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1004975
Title:
upstart needs more than 100 seconds to start a desktop
To manage notifications about this bug go to:
Here is a recent bootchart picture...
** Attachment added: bootchart
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164701/+files/bootchart.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here the logs from bootchart...
** Attachment added: bootchart logs
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164716/+files/asterix-precise-20120526-4.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And the upstart logs
** Attachment added: upstart logs
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1004975/+attachment/3164717/+files/upstart_logs.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for for your help. But I don't have the time to try this now.
After the next update of ubuntu I will try the on board sound card again.
For now I can live with the separate sound card.
Never touch a running system ;-)
--
You received this bug notification because you are a member of
Thank you for your hint. But I don't think that it will help.
Now I'm using natty (11.04) and there is no linux-backports-modules-
alsa-generic package any more.
And the problems with the on board sound card persists in natty.
Now I use a separate sound card to workaround the problems with the
** Changed in: mythexport (Ubuntu)
Status: Invalid = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/596539
Title:
mythexport does not honor an existing cutlist
To manage
What a pity. In my opinion a config should be a what it is, and no
script.
On the one hand it is a good thing that the mythexport-config can handle
anything you want (cause of the fact that it is a perl module). But on
the outher hand I would say end users should only have to decide which
will there be a fix for natty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742017
Title:
readline() on closed filehandle FILES warnings caused by multiarch
To manage notifications about this bug
I can confirm this. The same behaviour as go4linux described for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772992
Title:
quick-lounge-applet makes gnome-panel segfault on Ubuntu Natty
--
three different humans with nearly the same issue, that's confirmation
enough for me
** Changed in: quick-lounge-applet (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The problem is in pulseaudio not in alsa. After purging pulseaudio there
was no problem with the mic.
** Package changed: alsa-driver (Ubuntu) = pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Description:Ubuntu 10.10
Release:10.10
alsa-base:
Installiert: 1.0.23+dfsg-1ubuntu4
Kandidat:1.0.23+dfsg-1ubuntu4
Versionstabelle:
*** 1.0.23+dfsg-1ubuntu4 0
500 http://de.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
100
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/710077
Title:
no mic with ATI HDA SBx00 Azalia (VT1818S)
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Sorry but I had to buy new hardware cause the board gave up last summer.
There is nothing I can help any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/390158
Title:
[MSI MS-7329]
I've changed to another hardware cause my barbone got broken. So there
is nothing I can help with this issue any more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/302919
Title:
lcdproc: Futaba
The issue went gone with the mythbuntu weekly build (0.24).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/596242
Title:
mythvideo does not find files with german Umlaut (äöü)
--
ubuntu-bugs
Thanx for the information. When the Error-Message does not harm any
function I can ignore it. But in my opinion it should be a warning
instead of an error. In my case there is no nvidia card in the mythtv-
box. Why could there be an VDPAU-Error? Please think about it.
--
You received this bug
Hello pjw,
here is the information from my mythbuntu-box you requested.
ii libqtcore44:4.6.2-0ubuntu5.1Qt 4
core module
ii linux-image-2.6.32-25-generic 2.6.32-25.44 Linux
kernel image for version 2.6.32 on x86/x86_64
ii
Yes it does. For example a file like Singen ist schön.avi will be like
this Singen_ist_sch_n.avi. When there is more then one special german
character it gets more difficult get back the real meaning.
** Changed in: mythexport (Ubuntu)
Status: Incomplete = New
--
mythexport does not
Public bug reported:
Binary package hint: mythtv
Description:Ubuntu 10.04.1 LTS
Release:10.04
mythtv-frontend:
Installiert: 0.23.0+fixes24158-0ubuntu2
Kandidat: 0.23.0+fixes24158-0ubuntu2
Versions-Tabelle:
*** 0.23.0+fixes24158-0ubuntu2 0
500
--
VDPAU Error in mythfrontend.log although using radeon
https://bugs.launchpad.net/bugs/664559
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
I try it again:
The job runs and finishes correctly, if mythshutdown does not shutdown
automatically. So how should there
something wrong with the ffmpeg lines? (see attached mythexport_settings.cfg
and above you can see the log.)
In my opinion a mythexport job should stay in status running
Hi folks, I have the same problem with mounting nfs-shares on my working
machine to my htpc in the living room. There are 4 mount points for my
mythtv home entertainment and backup strategy.
/etc/fstab:
obelix:/var/lib/mythtv/music /var/lib/mythtv/music nfs _netdev,auto 0 0
I switched to the nouveau driver. After that I had resolution problems
(only 800x600 instead of 1280x1024). I found out that the kvm swich
cannot handle edid (ddc). So I substituted the kvm switch from Belkin
Switch2 USB (Model # F1DG102U-USB) to Digitus DC-11403. In the end the
issue of this bug
1 - 100 of 269 matches
Mail list logo
