[Bug 1971895] [NEW] Warning messages from stat printed on installation with no user crontabs
Public bug reported: On installation of cron on a new system, or (I expect) an upgrade with no user crontab files the following is printed: Setting up cron (3.0pl1-128.1ubuntu1.1) ... stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory stat: cannot stat '*': No such file or directory Warning: * is not a regular file! This is related to the fix for CVE-2017-9525 introduced in 3.0pl1-128.1ubuntu1.1. The for loop at line 66 of cron.postinst needs to have a guard like the following added to it: [ "$tab_name" = "*" ] && continue We have observed this with Bionic, I haven't checked any other Ubuntu releases. Cheers, Andrew ** Affects: cron (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971895 Title: Warning messages from stat printed on installation with no user crontabs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1971895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1
I pondered more on this issue this morning and decided to allow the service to fail to start on installation and remove. This is now fixed in 1.0.1-6. ** Changed in: mythtv-status (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879816 Title: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1879816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706362] Re: update-motd.d script prevents updating motd
Ugh. This evening I prepared a new package for Debian (1.0.1-2) which includes a patch for this: http://git.etc.gen.nz/cgi-bin/gitweb.cgi?p=mythtv-status.git;a=commit;h=089616c32247d109dc735da56838a6a4bc5d12f8 I'll be releasing version 1.0.2 which will also include this soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706362 Title: update-motd.d script prevents updating motd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/706362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879816] Re: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1
Hmm... I'm interested in hearing opinions here on how better to handle this situation. mythtv-status was unable to collect information from the mythtv-backend, so it was a legitimate failure. Should I be asking for the hostname to check during installation? Treat failure as acceptable? (Which might hide the issue) Something else? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879816 Title: package mythtv-status 1.0.1-1 failed to install/upgrade: installed mythtv-status package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1879816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
I'm hitting this issue on some new server hardware when trying to use lspci from pciutils with a 16.04 installation. I'm wondering of there has there been any progress on getting this fix released for Xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/1818816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count
We're still seeing the same issue on Ubuntu Trusty running the linux- image-3.19.0-30-generic kernel. Looking at this thread[0] on the Docker site which is referenced to in the kernel bugzilla for this issue, there is a reference[1] to a patch[2] on the netdev mailing list from 2015-11-05 by Francesco Ruggeri, later that day David Miller accepted it and queued it for -stable. The patch is currently in the master branch of Linus's tree, but hasn't made it into the 4.2 branch yet. The patch doesn't apply cleanly to the Canonical 3.19 branch, but it looks like it is mostly line skew. I haven't tried hacking it in yet. [0] https://github.com/docker/docker/issues/5618 [1] https://github.com/docker/docker/issues/5618#issuecomment-154334933 [2] http://www.spinics.net/lists/netdev/msg351337.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403152 Title: unregister_netdevice: waiting for lo to become free. Usage count To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1403152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1278666] [NEW] fai-do-scripts in fai-client can't detect Perl scripts
Public bug reported: fai-do-scripts has a case statement to determine if a script under the scripts directory should be read, and if it should, which log file to save the output to. It runs file -b on each file to determine the type of file, and then runs the case statement. The output of file -b changed, and no longer matches what fai-do-scripts expects. Please see my bug in the Debian BTS for the patch: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671899 (This was applied to FAI v4.0 but sadly Ubuntu is lagging behind on FAI.) ** Affects: fai (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278666 Title: fai-do-scripts in fai-client can't detect Perl scripts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fai/+bug/1278666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096252] Re: Should display local times
This issue is resolved in 0.10.4 in Debian Unstable... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096252 Title: Should display local times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1096252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096252] Re: Should display local times
Thanks Jan. Sadly the Date::Manip stuff doesn't listen to locale for the date format, you must explicitly set US or non-US when you init it. To avoid that silliness I've changed it to use %Y-%m-%d which is hopefully more generally acceptable. I've also added another patch that handles the Ends time for in progress recordings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096252 Title: Should display local times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1096252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096252] Re: Should display local times
This is now fixed in git. I'll push out a new release shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096252 Title: Should display local times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1096252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1096252] Re: Should display local times
Ah, I'm looking into the best way to resolve this now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1096252 Title: Should display local times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/1096252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
Hi, 0.10.2-2 has been released and uploaded to Debian Unstable. I'm not sure when it'll trickle through to Ubuntu. You can also fetch it from own repo, add this to an apt sources file: deb http://debian.etc.gen.nz sid main (See http://www.etc.gen.nz/projects/mythtv/mythtv-status.html for more details) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 596768] Re: package mythtv-status 0.9.2-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Ah, that'll happen in /var/run/motd.orig doesn't exist for some reason. That shouldn't cause the stop command to fail. I'll ignore failure there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/596768 Title: package mythtv-status 0.9.2-3 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/596768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
Could someone please provide me the output of http://localhost:6544/Status/GetStatusHTML (either ysuse lynx -dump or wget) and I'll see if I can fix up the date logic in mythtv-status rather than using a hack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
Thanks Ben, Ah ha that's the HTML version, how about http://localhost:6544/Status/GetStatus ? That is what mythtv-status will attempt to fetch as it is XML. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
Ah, I just clicked what comment #4 is about. The Data format issue in #10 does not affect the real mythtv-status. Better temporary solution: edit mythtv-status, search for http://; and change xml on that line to /Status/GetStatus. But I'll push out 0.10.2-2 shortly that is a much better fix (and includes a few other bug fixes). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
My recommendation would be to use the latest version of mythtv-status which supports MythTV 0.25. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: MythTV Status doesn't work with MythTV 0.25
I've release version 1.10.1 of mythtv-status (also in Debian Sid) that adds support for MythTV 0.25. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: MythTV Status doesn't work with MythTV 0.25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 945582] Re: mythtv-status fails to fetch from http://localhost:6544/xml:
Yes, I have a fixed version for this. I haven't released yet because I've been trying to resolve an issue with mythtv-status hanging around waiting to hear back from the MythTV backend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945582 Title: mythtv-status fails to fetch from http://localhost:6544/xml: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv-status/+bug/945582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455542] Re: Fails to find Disk information on .22
The only issue is that Ubuntu how has a different way of updating the MOTD than in Debian. -- Fails to find Disk information on .22 https://bugs.launchpad.net/bugs/455542 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455542] Re: Fails to find Disk information on .22
Grizzly: That sounds like a different issue, could you please raise a new bug report? Ken: What verions is installed? (Run: dpkg -l mythtv-status ) -- Fails to find Disk information on .22 https://bugs.launchpad.net/bugs/455542 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 437803] Re: mythtv-status script incorrectly attempts to report on storage using protocol version 32 and 39
Thank you, this is fixed in the upcoming 0.9.2 release of mythtv-status. ** Changed in: mythtv-status (Ubuntu) Status: New = Fix Committed ** Changed in: mythtv-status (Ubuntu) Assignee: (unassigned) = Andrew Ruthven (andrew-etc) -- mythtv-status script incorrectly attempts to report on storage using protocol version 32 and 39 https://bugs.launchpad.net/bugs/437803 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379500] Re: cronjob for mythtv-status send's me many mails after upgrade to jaunty
Hi, As the mythtv-status author, my preferred solution is to have mythtv- status run via update-motd. Just symlink'ing /usr/bin/mythtv-status into /etc/update-motd.d/ isn't the best solution - you won't pick up the configuration settings. However, the next version of mythtv-status will use a stand along config file which it tries to load, and that'll allow a much cleaner solution to this. In the meantime, the work around that Stefan gives is probably better (no need to restart cron though). Also, the latest version of mythtv- status (not in Ubuntu yet) checks if motd.new exists before it tries to move it in an attempt to reduce the race condition that is being hit. Cheers! -- cronjob for mythtv-status send's me many mails after upgrade to jaunty https://bugs.launchpad.net/bugs/379500 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 357485] [NEW] Must be installed to build from source
Public bug reported: To be able to build the libxmlbeans-java package you must have the libxmlbeans-java package installed. BUILD FAILED /usr/src/eucalyptus/xmlbeans-2.4.0/build.xml:239: Warning: Could not find file /usr/share/java/xmlbeans.jar to copy. And there is a build-dep on itself. Huh? ** Affects: xmlbeans (Ubuntu) Importance: Undecided Status: New -- Must be installed to build from source https://bugs.launchpad.net/bugs/357485 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327406] Re: MythTV.pm prints message in STDERR if UPnP is used
Hi Dave, Given the number of users of mythtv-status that have asked me about the output I'd say the answer is absolutely not. This is a debugging message, it shouldn't be displayed to the users. They don't care if UPnP has been used as long as they receive the correct response. Cheers! -- MythTV.pm prints message in STDERR if UPnP is used https://bugs.launchpad.net/bugs/327406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327406] [NEW] MythTV.pm prints message in STDERR if UPnP is used
Public bug reported: Binary package hint: libmyth-perl Currently whenever MythTV.pm falls back to using UPnP it prints a message to STDERR stating this fact. This is totally unrequired and annoys users. The attached patch stops this behaviour. This bug has been reported to MythTV - http://svn.mythtv.org/trac/ticket/6246 but it is currently annoying users so it'd be great if it could go into Ubuntu sooner than MythTV will apply it. ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- MythTV.pm prints message in STDERR if UPnP is used https://bugs.launchpad.net/bugs/327406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327406] Re: MythTV.pm prints message in STDERR if UPnP is used
** Attachment added: 0001-Don-t-print-a-message-to-STDERR-if-we-re-using-UPnP.patch http://launchpadlibrarian.net/22425354/0001-Don-t-print-a-message-to-STDERR-if-we-re-using-UPnP.patch -- MythTV.pm prints message in STDERR if UPnP is used https://bugs.launchpad.net/bugs/327406 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327405] [NEW] MythTV.pm prints message in STDERR if UPnP is used
*** This bug is a duplicate of bug 327406 *** https://bugs.launchpad.net/bugs/327406 Public bug reported: Binary package hint: libmyth-perl Currently whenever MythTV.pm falls back to using UPnP it prints a message to STDERR stating this fact. This is totally unrequired and annoys users. The attached patch stops this behaviour. This bug has been reported to MythTV - http://svn.mythtv.org/trac/ticket/6246 but it is currently annoying users so it'd be great if it could go into Ubuntu sooner than MythTV will apply it. ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 327406 MythTV.pm prints message in STDERR if UPnP is used -- MythTV.pm prints message in STDERR if UPnP is used https://bugs.launchpad.net/bugs/327405 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311532] Re: the mythtv status cron script sends an annoying email every hour.
I've submitted a patch for libmyth-perl which resolves this issue #327406. -- the mythtv status cron script sends an annoying email every hour. https://bugs.launchpad.net/bugs/311532 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 327409] [NEW] libmyth-perl package should be called libmythtv-perl
Public bug reported: Binary package hint: libmyth-perl The Perl module is called MythTV.pm, to be consistent with other packages the Ubuntu package should be called libmythtv-perl. ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- libmyth-perl package should be called libmythtv-perl https://bugs.launchpad.net/bugs/327409 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326162] Re: mythtv-status clobbers other motd update scripts
Hi, Yes, I agree that on Jaunty this is the right way to solve this issue. I'm also quite keen to port update-motd to Debian so I can resolve this issue (although it hasn't been reported on Debian) there. Cheers! -- mythtv-status clobbers other motd update scripts https://bugs.launchpad.net/bugs/326162 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311532] Re: the mythtv status cron script sends an annoying email every hour.
If mythtv-status can find the backend using UPnP then this is a bug with MythTV.pm (in the libmyth-perl package). That is where this warning message is coming from. -- the mythtv status cron script sends an annoying email every hour. https://bugs.launchpad.net/bugs/311532 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311532] Re: the mythtv status cron script sends an annoying email every hour.
I say warning message, in the MythTV.pm code there is a comment above the line that emits the message that states alert the user - does the user actually care in this case? I think not. :) -- the mythtv status cron script sends an annoying email every hour. https://bugs.launchpad.net/bugs/311532 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251330] Re: mythtv-status init script lacks the 'status' action
After a bit more consideration the status could report if the motd has been updated in the past x minutes if the ENABLE flag is set. Would this be inline with the Ubuntu policy? -- mythtv-status init script lacks the 'status' action https://bugs.launchpad.net/bugs/251330 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 251330] Re: mythtv-status init script lacks the 'status' action
The status code that is being added to the init.d script is somewhat misleading. mythtv-status doesn't actually have a daemon to run... -- mythtv-status init script lacks the 'status' action https://bugs.launchpad.net/bugs/251330 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237564] Re: mythtv-status should be run as the same user as mythtv
But what happens if you don't have a frontend on the box? What happens if the .mythtv/config.xml still doesn't exist? My preference is use a modified MythTV.pm which doesn't require accessing the database. I've made the modification, I just need to submit the patch to the MythTV trac instance. The second option is to have all the UPnP modules installed so that UPnP can be used. Of course, then MythTV.pm still needs to be modified to not tell the user that it has used UPnP. (More patches I have sitting here waiting to be submitted.) -- mythtv-status should be run as the same user as mythtv https://bugs.launchpad.net/bugs/237564 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 237564] Re: mythtv-status should be run as the same user as mythtv
mythtv-status could run as the mythtv daemon user, but does the mythtv daemon user have the config.xml file? (I'm not running 0.21 yet, so can't check). As Björn points out you can't just have the cron job run the init script as the mythtv user due to needing to write to /etc/motd, but the init script could run mythtv-status as the mythtv user. Why have the init.d script? So that on system bootup the motd is set correctly rather than having to wait for the cronjob to run. I'd still prefer to see MythTV.pm fixed. This would solve this and some other problems. Given the way that I'm using MythTV.pm, it has no need what so ever to contact the database, so config.xml is not actually required for the current user case. I can tell MythTV.pm where the host is (because mythtv-status knows), but this patch is unlikely to hit the 0.21-fixes branch. -- mythtv-status should be run as the same user as mythtv https://bugs.launchpad.net/bugs/237564 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 198962] [NEW] Newer version available
Public bug reported: Binary package hint: mythtv-status The version upstream (and in Debian) is up to 0.7.1, which adds more functionality, better handling of bogus data and more error checking. Please consider this a wishlist bug. ** Affects: mythtv-status (Ubuntu) Importance: Undecided Status: New -- Newer version available https://bugs.launchpad.net/bugs/198962 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86581] Re: Glom has issues if DB user is missing access rights
On Fri, 2007-03-09 at 22:27 +, Murray Cumming wrote: I really want to investigate and fix this issue, but I really need those specific instructions to reproduce it. Hi, I was actually preparing these instructions last week. Went through a couple of test runs, and had differing results, so I want to double check them. My wife is almost due with our first child, so my spare time is reducing. But I'll try and get these instructions through to you soon. Cheers! -- Andrew Ruthven, Wellington, New Zealand At home: [EMAIL PROTECTED] | This space intentionally |left blank. -- Glom has issues if DB user is missing access rights https://launchpad.net/bugs/86581 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86581] Re: Glom has issues if DB user is missing access rights
On Fri, 2007-02-23 at 07:49 +, Murray Cumming wrote: So is this actually two problems? One about what happens when the utility executable are missing, and one about what happens when a postgres user has particular postgres access rights? Could you provide more information about that second problem, such as the steps you take and what you see, please? Maybe in a separate bug report. Hi, No, this is only about missing rights. Nothing to do with missing executables. I think you have misunderstood me because there is a user access right/flag called createdb and a utility called createdb. My DB user was missing the right/flag createdb. I added right/flag createdb and then I found I was missing the createrole role. The behaviour I noticed is reported in my original description of this bug report. To reproduce this behaviour I expect you could create a DB user (using createuser) that has none of these rights, then try and create a new Glom DB using that user. Cheers! -- Andrew Ruthven Wellington, New Zealand At home: [EMAIL PROTECTED] | This space intentionally |left blank. -- Glom has issues if DB user is missing access rights https://launchpad.net/bugs/86581 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 86581] Re: Glom has issues if DB user is missing access rights
Gidday, On Thu, 2007-02-22 at 12:13 +, Murray Cumming wrote: If the DB user you use to connect to PostgreSQL is missing required access rights then Glom has some serious issues... I'm not sure what you mean. Are you talking about the Linux user, or a PostgreSQL user, or just about the availability (or access to) the Postgres command-line utilities that you mention below? The user in the database. If you use psql (connecting using the user you want to use with glom, which defaults to your Linux username) and use: select * from pg_roles where rolname = current_user Then that user/role needs to have rolcreatedb and rolcreaterole. If createdb is missing then Glom fails to create the database This should be avoided by the incomplete-installation detection in the latest version (1.3.9). Could you check that please, though you might want to wait for yet another version because the Ubuntu Glom maintainer is making some useful changes at the moment. Okay, I'll give it a go when glom 1.3.9 appears in Feisty. Thanks! -- Andrew Ruthven, Wellington, New Zealand At home: [EMAIL PROTECTED] | This space intentionally |left blank. -- Glom has issues if DB user is missing access rights https://launchpad.net/bugs/86581 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86581] Glom has issues if DB user is missing access rights
Public bug reported: Binary package hint: glom Package: glom Version: 1.3.8-0ubuntu1 Severity: normal If the DB user you use to connect to PostgreSQL is missing required access rights then Glom has some serious issues... If createdb is missing then Glom fails to create the database (obviously) but still has the state files on the disk. If you then try to open that database again Glom complains bitterly. If createrole is missing then Glom has a segmentation fault and then the next time you try to use the database the required roles are missing (even if you add the createrole role to your DB user). Perhaps these roles could be checked for before the database is created and a suitable error message (with resolution directions) provided to the user. Cheers! ** Affects: glom (Ubuntu) Importance: Undecided Status: Unconfirmed -- Glom has issues if DB user is missing access rights https://launchpad.net/bugs/86581 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 86582] Glom suggests postgresql-8.2, but doesn't use the right port.
Public bug reported: Binary package hint: glom Package: glom Version: 1.3.8-0ubuntu1 Severity: normal Glom suggests postgresql-8.2 which listens on port 5434 by default. When Glom attempts to connect to the PostgreSQL database it tries ports 5432 and 5433, but *not* 5434. Unfortunately I don't see any way to tell Glom to use a different port via the Database specification dialog. It looks like the standard of using hostname:port doesn't work. While I could (and will) change the port that PostgreSQL 8.2 uses, I don't think that is the correct long-term solution. Glom should really try port 5434 now as well... ** Affects: glom (Ubuntu) Importance: Undecided Status: Unconfirmed -- Glom suggests postgresql-8.2, but doesn't use the right port. https://launchpad.net/bugs/86582 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
