[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
Alright, thank you. My apologies for the accidentally inflating the
issue, I was not thinking through my comment much when I posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
I thought this had been fixed, but I ran into something else very
similar today:
When I had a symlink set for ~/.cache/deja-dup, deja-dup actually
_deleted_ this symlink, and still filled up my home folder. I ran out of
space and the backup failed.
Perhaps this is why it was succeeding for me, just by coincidence I had
enough space at the time?
Or would it be better to make a new issue for this seeming deletion of
symbolic links?
deja-dup 34.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
When this last occurred for me, it happened after the backup was
complete, or at least after the backup had been running for a while. I'm
unsure if it was during, before or after the 'verification' phase.
Just now, when running the command you posted, the error did not occur.
I haven't had this error anyways for quite some time since I've been
using the workaround of having an rbind mount, but just now I re-did the
symlink which caused the error before, and the error did not occur. I'm
now using deja-dup 34.2 in Gentoo, and when it originally occurred I was
using an earlier version of deja-dup in Ubuntu. I'm not sure if it's
completely fixed for me, if my different setup can no longer reproduce
the error, or if it just worked this one time, so if anyone else who had
experienced in the past could test with deja-dup 34.2, that would
probably be best.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1217959] Re: 'metadata' file not found when creating backup ("Could not restore ‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
I've worked around this by using a bind mount instead of a symlink.
Something like 'sudo mount --rbind /run/media/daboross/external/deja-
dup-cache ~/.cache/deja-dup' works. While I do have to re-do this every
time I mount the external drive and start a backup, it at least works.
If you also do a `chmod 500 ~/.cache/deja-dup` when it's unmounted,
deja-dup will be unable to write any files to the unmounted directory
and it will fail early - so you can then mount it and re-start the
backup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1217959
Title:
'metadata' file not found when creating backup ("Could not restore
‘/home/user /.cache/deja-dup/metadata’: File not found in backup"
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1217959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253167] Re: Rhythmbox sort by "Album Artist" for guest/compilations
This is perfectly possible in banshee - I don't really see why it's so hard to implement for Rhythmbox. Is there anything in particular which is blocking this being an added feature? This is really the only thing stopping me from switching to Rhythmbox from Banshee now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253167 Title: Rhythmbox sort by "Album Artist" for guest/compilations To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/253167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172837] Re: Python appindicator doesn't work in 13.04 when run as root
*** This bug is a duplicate of bug 1289204 *** https://bugs.launchpad.net/bugs/1289204 Correct me if I'm wrong, but I believe bug #1289204 is about local/global app menus, not about app indicators at all. These two bugs do seem to be the same kind of issue, but both mention different symptoms. Should/will #1289204 be edited to include app indicators as well as local/global menus? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172837 Title: Python appindicator doesn't work in 13.04 when run as root To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1120344] Re: usb-creator-gtk crashes upon installing the bootloader to usb stick
This happens to me as well with ubuntu 13.04 amd64 using ubuntu-gnome image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1120344 Title: usb-creator-gtk crashes upon installing the bootloader to usb stick To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1120344/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180297] Re: Opening facebook "Success" page in external browser
Changing Facebook facebook account-plugins .*facebook\.com generic-oauth oauth2 user_agent www.facebook.com /dialog/oauth https://www.facebook.com/connect/login_success.html popup ['publish_stream','read_stream','status_update','user_photos','friends_photos','xmpp_login'] 302061903208115 to Facebook facebook account-plugins .*facebook\.com generic-oauth oauth2 user_agent www.facebook.com /dialog/oauth https://www.facebook.com/connect/login_success.html popup ['publish_stream','read_stream','status_update','user_photos','friends_photos','xmpp_login'] 302061903208115 ['https','http'] in /usr/share/accounts/providers/facebook.provider worked for me to fix it. Everyone who this isn't working for, are you adding the ['https','http'] inside the of the xml document? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180297 Title: Opening facebook "Success" page in external browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1180297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1172837] [NEW] Python appindicator doesn't work in 13.04 when run as root
Public bug reported: I have created a simple python program that uses the appinidicator function of unity (attached). When I run it as a regular user, it works perfectly. But when I use 'sudo ./testindicator.py' instead of '/testindicator.py' it doesn't show up. This only happens while running the latest version of unity in ubuntu 13.04. This is what it looks like from command-line: daboross@DaboUbuntu:~$ ./testindicator/testindicator.py ^CTraceback (most recent call last): File "./testindicator/testindicator.py", line 20, in gtk.main() KeyboardInterrupt daboross@DaboUbuntu:~$ sudo ./testindicator/testindicator.py ^CTraceback (most recent call last): File "./testindicator/testindicator.py", line 20, in gtk.main() KeyboardInterrupt (testindicator.py:16215): libappindicator-WARNING **: Unable to send signal for NewStatus: The connection is closed daboross@DaboUbuntu:~$ I used ctrl-c to stop the program. From the time when I used the first command to when I used ctrl-c, an indicator icon did appear. It didn't when I used `sudo`. There is another program that I am using (pyAlienFX), that needs to run an appindicator as root. In 13.04, it seems that this does not work. This bug does not occur when I used `sudo` and am on Ubuntu 12.04. This is the output of unity --version: daboross@DaboUbuntu:~$ unity --version unity 7.0.0 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Apr 25 11:19:15 2013 InstallationDate: Installed on 2013-04-20 (5 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130419) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 appindicator apport-bug python raring ** Attachment added: "This is the python indicator I tested with." https://bugs.launchpad.net/bugs/1172837/+attachment/3653557/+files/testindicator.py -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1172837 Title: Python appindicator doesn't work in 13.04 when run as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1172837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
I am getting this error in 12.10, usually when running some programs on SandyBridge mobile, and also others with bumblebee. I have a optimus laptop. I haven't gotten this error while only running with bumblebee. When it happens I get no graphics glitches or anything other then my computer suddenly stops responding for around 5 seconds. Then I get around 10-15 windows that are asking me if my system has hung recently. After I say "yes" and then "around once a day"(I think that is the option), I get a system report saying that apport-gpu-error.py has crashed. with the "bug title": [sandybridge-m-gt2] GPU lockup IPEHR: 0x4218 IPEHR: 0x01000 Next time this happens I will record everything the bug report says. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1140716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
I get these a lot with ubuntu 12.10, though they aren't really a problem as I have a script run with crontab to delete them on boot `@reboot rm ~/.goutputstream-*` in `crontab -e`. It has something to do with file management, I think. just speculating, but because everyone who has these have them with some process that edits files, like Ubuntu one/dropbox, or when booting up/shutting down. What if the process that creates goutputstream for changing files hasn't fully loaded or is shut down in the middle of an operation? (just speculating). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
