[Touch-packages] [Bug 1741515] [NEW] units: starting suspend.target should not fail when suspend is succesful
Public bug reported: Since systemd 233 the behavior of BindsTo is changed which can cause suspend.target to fail when suspend.service is successful. Please apply patch: https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2 which is fixing: https://github.com/systemd/systemd/pull/6678 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd ** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1741515 Title: units: starting suspend.target should not fail when suspend is succesful Status in systemd package in Ubuntu: New Bug description: Since systemd 233 the behavior of BindsTo is changed which can cause suspend.target to fail when suspend.service is successful. Please apply patch: https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2 which is fixing: https://github.com/systemd/systemd/pull/6678 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741515/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Bug 1741515] [NEW] units: starting suspend.target should not fail when suspend is succesful
Public bug reported: Since systemd 233 the behavior of BindsTo is changed which can cause suspend.target to fail when suspend.service is successful. Please apply patch: https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2 which is fixing: https://github.com/systemd/systemd/pull/6678 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd ** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1741515 Title: units: starting suspend.target should not fail when suspend is succesful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741515/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1741515] [NEW] units: starting suspend.target should not fail when suspend is succesful
Public bug reported: Since systemd 233 the behavior of BindsTo is changed which can cause suspend.target to fail when suspend.service is successful. Please apply patch: https://github.com/systemd/systemd/commit/64a36ae4b1dd23474dd7ea261381ac437b24fac2 which is fixing: https://github.com/systemd/systemd/pull/6678 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: systemd ** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741515 Title: units: starting suspend.target should not fail when suspend is succesful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1741515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: uncorrectable errors in Raid 10
Hi, I think just some XWayland Nouveau bug: Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: TRAP ch 22 [007d08d000 Xwayland[781]] Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC0/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC1/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC2/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC3/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: gr: GPC0/TPC4/TEX: 8041 Nov 23 12:46:26 bigbox kernel: nouveau :01:00.0: fifo: read fault at 000586 engine 00 [GR] client 15 [GPC0/PE_4] reason 02 [PTE] on channel 22 [007d08d000 Xwayland[781]] Steffen Am 23.11.2017 um 13:14 schrieb Qu Wenruo: On 2017年11月23日 20:02, Steffen Sindzinski wrote: Hi, I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I will run it this night again. Any kernel backtrace about the crash? IIRC user space program like btrfs check should not trigger a kernel crash. The result until crash was: Checking filesystem on /dev/sdd2 UUID: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358 ERROR: extent[15923092037632, 73728] referencer count mismatch (root: 260, owner: 3631467, offset: 1019904) wanted: 4, have: 6 ERROR: extent[16078964924416, 69632] referencer count mismatch (root: 260, owner: 4086589, offset: 4296704) wanted: 5, have: 7 This is known bug, please use this branch instead. https://github.com/adam900710/btrfs-progs/tree/lowmem_fix Thanks, Qu Steffen Am 22.11.2017 um 17:42 schrieb Chris Murphy: On Wed, Nov 22, 2017 at 9:38 AM, Steffen Sindzinski <stes...@gmail.com> wrote: Hello, I did btrfs check --readonly on both disk without finding any error. To reconfirm I did a scrub again which still has found 2 uncorrectable errors. Try --mode=lowmem option with btrfs-progs 4.3.3 or better 4.14. This is a new implementation of btrfs check and sometimes it comes up with different results. It's strange that there's only this error found by scrub and not by btrfs check which should be fully checking all metadata for sanity, and in the process it would surely hit a bad checksum. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: uncorrectable errors in Raid 10
Hi, I updated to btrfs-progs v4.14-5-gf09e98a3. Unfortunately after 10h Gnome desktop / Arch crashed with btrfs check --lowmem unfinished. I will run it this night again. The result until crash was: Checking filesystem on /dev/sdd2 UUID: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358 ERROR: extent[15923092037632, 73728] referencer count mismatch (root: 260, owner: 3631467, offset: 1019904) wanted: 4, have: 6 ERROR: extent[16078964924416, 69632] referencer count mismatch (root: 260, owner: 4086589, offset: 4296704) wanted: 5, have: 7 Steffen Am 22.11.2017 um 17:42 schrieb Chris Murphy: On Wed, Nov 22, 2017 at 9:38 AM, Steffen Sindzinski <stes...@gmail.com> wrote: Hello, I did btrfs check --readonly on both disk without finding any error. To reconfirm I did a scrub again which still has found 2 uncorrectable errors. Try --mode=lowmem option with btrfs-progs 4.3.3 or better 4.14. This is a new implementation of btrfs check and sometimes it comes up with different results. It's strange that there's only this error found by scrub and not by btrfs check which should be fully checking all metadata for sanity, and in the process it would surely hit a bad checksum. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
uncorrectable errors in Raid 10
Hello, I have done a scrub on my Btrfs Raid 10 and have 2 uncorrectable errors. In fact I cannot access 2 directories, even as root, permission is denied and all directory attributes in ls -la are . Before I have run this filesystem as Raid 1 with 3 disks without any problems for more than a year. Scrubbed regularily. A month ago I added a fouth HDD and balanced to Raid10. I am not sure if I did a scub afterwards, but I usualy do. Now it found that errors. Smart status of HDDs is healthy. The 2 directories were read-only for some years and not even read in the last month. What can I do now? Should I do a btrfs rescue? Which device, it is a raid 10? Probably my files are OK, only the directories I cannot access. How to recover the files? Thanks in advance! Steffen Here is my data: Linux bigbox 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux btrfs-progs v4.12 Label: 'Videos' uuid: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358 Total devices 4 FS bytes used 1.44TiB devid3 size 1.82TiB used 785.56GiB path /dev/sdc2 devid4 size 1.82TiB used 785.56GiB path /dev/sde2 devid5 size 1.82TiB used 785.56GiB path /dev/sdd2 devid6 size 1.36TiB used 785.56GiB path /dev/sdf1 Data, RAID10: total=1.51TiB, used=1.43TiB System, RAID10: total=128.00MiB, used=192.00KiB Metadata, RAID10: total=21.00GiB, used=17.76GiB GlobalReserve, single: total=512.00MiB, used=0.00B % sudo btrfs scrub start -Bd / scrub device /dev/sdc2 (id 3) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:27 total bytes scrubbed: 568.86GiB with 0 errors scrub device /dev/sde2 (id 4) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:28 total bytes scrubbed: 702.88GiB with 1 errors error details: verify=1 corrected errors: 0, uncorrectable errors: 1, unverified errors: 0 scrub device /dev/sdd2 (id 5) done scrub started at Sun Nov 19 08:43:21 2017 and finished after 01:48:00 total bytes scrubbed: 737.74GiB with 1 errors error details: verify=1 corrected errors: 0, uncorrectable errors: 1, unverified errors: 0 scrub device /dev/sdf1 (id 6) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:28 total bytes scrubbed: 506.02GiB with 0 errors [4.985712] BTRFS: device label Videos devid 6 transid 772463 /dev/sdf1 [4.985882] BTRFS: device label Videos devid 4 transid 772463 /dev/sde2 [4.986541] BTRFS: device label Videos devid 5 transid 772463 /dev/sdd2 [4.986713] BTRFS: device label Videos devid 3 transid 772463 /dev/sdc2 [5.007986] BTRFS info (device sdc2): disk space caching is enabled [5.007988] BTRFS info (device sdc2): has skinny extents [5.149910] BTRFS info (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3 [5.149916] BTRFS info (device sdc2): bdev /dev/sde2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3 [ 25.482987] BTRFS info (device sdc2): use lzo compression [ 25.482990] BTRFS info (device sdc2): disk space caching is enabled [57830.611730] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [57830.611732] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [57830.611734] BTRFS error (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 4 [57832.688689] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sdd2 [57870.488081] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [57870.488083] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [57870.488085] BTRFS error (device sdc2): bdev /dev/sde2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 4 [57870.500114] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sde2 [88979.005712] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [88979.005718] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [88979.005720] BTRFS error (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 5 [88979.036670] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sdd2 [89026.609561] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [89026.609563] BTRFS warning (device
uncorrectable errors in Raid 10
Hello, I have done a scrub on my Btrfs Raid 10 and have 2 uncorrectable errors. In fact I cannot access 2 directories, even as root, permission is denied and all directory attributes in ls -la are . Before I have run this filesystem as Raid 1 with 3 disks without any problems for more than a year. Scrubbed regularily. A month ago I added a fouth HDD and balanced to Raid10. I am not sure if I did a scub afterwards, but I usualy do. Now it found that errors. Smart status of HDDs is healthy. The 2 directories were read-only for some years and not even read in the last month. What can I do now? Should I do a btrfs rescue? Which device, it is a raid 10? Probably my files are OK, only the directories I cannot access. How to recover the files? Thanks in advance! Steffen Here is my data: Linux bigbox 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:04:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux btrfs-progs v4.12 Label: 'Videos' uuid: 4fafd0d4-7dd9-4dcc-9a33-5f1ad9555358 Total devices 4 FS bytes used 1.44TiB devid 3 size 1.82TiB used 785.56GiB path /dev/sdc2 devid 4 size 1.82TiB used 785.56GiB path /dev/sde2 devid 5 size 1.82TiB used 785.56GiB path /dev/sdd2 devid 6 size 1.36TiB used 785.56GiB path /dev/sdf1 Data, RAID10: total=1.51TiB, used=1.43TiB System, RAID10: total=128.00MiB, used=192.00KiB Metadata, RAID10: total=21.00GiB, used=17.76GiB GlobalReserve, single: total=512.00MiB, used=0.00B % sudo btrfs scrub start -Bd / scrub device /dev/sdc2 (id 3) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:27 total bytes scrubbed: 568.86GiB with 0 errors scrub device /dev/sde2 (id 4) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:28 total bytes scrubbed: 702.88GiB with 1 errors error details: verify=1 corrected errors: 0, uncorrectable errors: 1, unverified errors: 0 scrub device /dev/sdd2 (id 5) done scrub started at Sun Nov 19 08:43:21 2017 and finished after 01:48:00 total bytes scrubbed: 737.74GiB with 1 errors error details: verify=1 corrected errors: 0, uncorrectable errors: 1, unverified errors: 0 scrub device /dev/sdf1 (id 6) canceled scrub started at Sun Nov 19 08:43:21 2017 and was aborted after 01:58:28 total bytes scrubbed: 506.02GiB with 0 errors [ 4.985712] BTRFS: device label Videos devid 6 transid 772463 /dev/sdf1 [ 4.985882] BTRFS: device label Videos devid 4 transid 772463 /dev/sde2 [ 4.986541] BTRFS: device label Videos devid 5 transid 772463 /dev/sdd2 [ 4.986713] BTRFS: device label Videos devid 3 transid 772463 /dev/sdc2 [ 5.007986] BTRFS info (device sdc2): disk space caching is enabled [ 5.007988] BTRFS info (device sdc2): has skinny extents [ 5.149910] BTRFS info (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3 [ 5.149916] BTRFS info (device sdc2): bdev /dev/sde2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3 [ 25.482987] BTRFS info (device sdc2): use lzo compression [ 25.482990] BTRFS info (device sdc2): disk space caching is enabled [57830.611730] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [57830.611732] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [57830.611734] BTRFS error (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 4 [57832.688689] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sdd2 [57870.488081] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [57870.488083] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [57870.488085] BTRFS error (device sdc2): bdev /dev/sde2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 4 [57870.500114] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sde2 [88979.005712] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [88979.005718] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sdd2, sector 338986176: metadata leaf (level 0) in tree 318 [88979.005720] BTRFS error (device sdc2): bdev /dev/sdd2 errs: wr 0, rd 0, flush 0, corrupt 0, gen 5 [88979.036670] BTRFS error (device sdc2): unable to fixup (regular) error at logical 17478699876352 on dev /dev/sdd2 [89026.609561] BTRFS warning (device sdc2): checksum/header error at logical 17478699876352 on dev /dev/sde2, sector 348423360: metadata leaf (level 0) in tree 318 [89026.609563] BTRFS warning (device sdc2):
[Bug 1278280] Re: ubuntu-release-upgrader crashes with DistUpgrade/sourceslist.py, line 416, in save : UnicodeEncodeError: 'ascii' codec can't encode characters in position 97-114: ordinal not in ran
No solution so far? I deleted all files in /etc/apt/sources.list.d/ but still same. In sources.list is just the standard stuff. Nothing with unicode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1278280 Title: ubuntu-release-upgrader crashes with DistUpgrade/sourceslist.py, line 416, in save : UnicodeEncodeError: 'ascii' codec can't encode characters in position 97-114: ordinal not in range(128) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1278280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[no subject]
-- To unsubscribe from this list: send the line unsubscribe linux-btrfs in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 1179801] Re: Can't connect to A2DP Device in Ubuntu 13.04
It throws an dbus error: GDBus.Error:org.bluez.Error.Failed: Stream setup failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179801 Title: Can't connect to A2DP Device in Ubuntu 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1179801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058760] Re: unmatched entries for dovecot login
patch #1 worked for me as well -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1058760 Title: unmatched entries for dovecot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1058760/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1058760] Re: unmatched entries for dovecot login
patch #1 worked for me as well -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058760 Title: unmatched entries for dovecot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1058760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?
For me this bug appears on a (slow) BTRFS partition on hard disk mounted as root. Apperantly lightdm has timing proplems and there is no fix for it. As a workaround, respawing as of #48 worked for me as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: New Status in “lightdm” package in Ubuntu: Confirmed Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1133179] [NEW] btrfs balance crashes Ubuntu 12.10 when online changing raid level
Public bug reported: No matter if I change the btrfs raid level to 0 or 1 Ubuntu 12.10 crashes. The screen is frozen and btrfs balance stopped. After turning off and on btrfs continues the balance job without any further crashes or errors. What I have: btrfs with @, @home, @opt, @var all mounted respectively What I do: sudo btrfs balance start -dconvert=raid0 -mconvert=raid1 / or sudo btrfs balance start -dconvert=raid1 -mconvert=raid1 / The crash happend once every time I changed the raid level on a root mounted btrfs. There is no /var/log/syslog or dmesg message about this. ** Affects: btrfs-tools (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/1133179 Title: btrfs balance crashes Ubuntu 12.10 when online changing raid level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1133179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969489] Re: lightdm tries (and fails) to start too early?
For me this bug appears on a (slow) BTRFS partition on hard disk mounted as root. Apperantly lightdm has timing proplems and there is no fix for it. As a workaround, respawing as of #48 worked for me as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1133179] Re: btrfs balance crashes Ubuntu 12.10 when online changing raid level
I have just installed btrfs-tools 0.20 from a PPA and it seems to fix this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1133179 Title: btrfs balance crashes Ubuntu 12.10 when online changing raid level To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1133179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 I have the same problem but btrfs as filesystem on a normal hard disk. The btrfs overhead seems to slow down the boot and lightdm is respawning once then exiting. Switching to btrfs raid 0 seems to fix but I want raid 1 or no raid at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 Status in “lightdm” package in Ubuntu: Confirmed Bug description: Ubuntu 12.10 doesn't load correctly because lightdm shows only a mouse pointer and a blinking command-line cursor. I don't know if this is only Ubuntu 12.10 specific bug, because a similar error appeared on my friend's computer back in 2011 on Ubuntu 11.10. However, switching to a command line and restarting lightdm solves the problem per instance. Also rebooting the device solves it, but also only for the specific boot. Another reboot ends with the same black screen with a working mouse pointer and a blinking cursor. I am using Asus Zenbook ux32vd (Intel HD Graphics 4000 + not used Nvidia GT620M - Optimus technology). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1066410] Re: lightdm doesn't load correctly on Ubuntu 12.10
*** This bug is a duplicate of bug 969489 *** https://bugs.launchpad.net/bugs/969489 I have the same problem but btrfs as filesystem on a normal hard disk. The btrfs overhead seems to slow down the boot and lightdm is respawning once then exiting. Switching to btrfs raid 0 seems to fix but I want raid 1 or no raid at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066410 Title: lightdm doesn't load correctly on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
For me it started to work partly yesterday. Because I did a lot of stuff, I cannot say why. First I tried out the gnome3 PPA. To uninstall this I had to reinstall ubuntu-desktop. This seemed not to solve the problem. I also read about an time server problem which would cause that gnome-online-accounts could not resolve all related hosts. I updated the system time. Furthermore there have been some related updates. In the end, gnome-online-accounts (Ubuntu) were able to connect to all (gtalk, hotmail, facebook). But now my google calendar in thunderbird disappeared and Thunderbird is asking always for a password, which it did not before. Now I switched back to Evolution, there now the addresses are working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook Status in “empathy” package in Ubuntu: Confirmed Bug description: This communicator does not connect with anything my online accounts. Facebook, Google, Outlook. Everything not working. I reistalled this program, clear configuration, logout and login again on accounts, clear applications in Outlook and Facebook. On main program window I see a this stuff: http://ubuntuone.com/7C06coFpCBdo6ic9Zeue2U Translate from google translate: Nie podano powodu - Not reason given Należy zmienić stan, aby wyświetlić kontakty - You must change the status to view the contacts Przejdź do trybu online - Go online Button Go online not working. Today. I was started Empathy in terminal. And when I pressed button Gon Online I see this; lukasz@lukasz-Lenovo-G565:~$ empathy (empathy:6635): tp-glib-CRITICAL **: tp_asv_get_uint32: assertion `asv != NULL' failed (empathy:6635): tp-glib-CRITICAL **: tp_asv_get_boxed: assertion `asv != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
For me it started to work partly yesterday. Because I did a lot of stuff, I cannot say why. First I tried out the gnome3 PPA. To uninstall this I had to reinstall ubuntu-desktop. This seemed not to solve the problem. I also read about an time server problem which would cause that gnome-online-accounts could not resolve all related hosts. I updated the system time. Furthermore there have been some related updates. In the end, gnome-online-accounts (Ubuntu) were able to connect to all (gtalk, hotmail, facebook). But now my google calendar in thunderbird disappeared and Thunderbird is asking always for a password, which it did not before. Now I switched back to Evolution, there now the addresses are working. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
For me it started to work partly yesterday. Because I did a lot of stuff, I cannot say why. First I tried out the gnome3 PPA. To uninstall this I had to reinstall ubuntu-desktop. This seemed not to solve the problem. I also read about an time server problem which would cause that gnome-online-accounts could not resolve all related hosts. I updated the system time. Furthermore there have been some related updates. In the end, gnome-online-accounts (Ubuntu) were able to connect to all (gtalk, hotmail, facebook). But now my google calendar in thunderbird disappeared and Thunderbird is asking always for a password, which it did not before. Now I switched back to Evolution, there now the addresses are working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
I am experiencing the same since 1 or 2 weeks ago. Before I was running 12.10 (upgraded from 12.04) and empathy worked. Probably connected to this bug is the bug that evolution always asks for passphrases of several accounts. How can I dump that stupid Ubuntu accounts and get the original application based accounts? Since the introduction of the ubuntu online accounts it is broken and gets fixed after a few months. Please don't bug users with such crap alpha version software. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook Status in “empathy” package in Ubuntu: Incomplete Bug description: This communicator does not connect with anything my online accounts. Facebook, Google, Outlook. Everything not working. I reistalled this program, clear configuration, logout and login again on accounts, clear applications in Outlook and Facebook. On main program window I see a this stuff: http://ubuntuone.com/7C06coFpCBdo6ic9Zeue2U Translate from google translate: Nie podano powodu - Not reason given Należy zmienić stan, aby wyświetlić kontakty - You must change the status to view the contacts Przejdź do trybu online - Go online Button Go online not working. Today. I was started Empathy in terminal. And when I pressed button Gon Online I see this; lukasz@lukasz-Lenovo-G565:~$ empathy (empathy:6635): tp-glib-CRITICAL **: tp_asv_get_uint32: assertion `asv != NULL' failed (empathy:6635): tp-glib-CRITICAL **: tp_asv_get_boxed: assertion `asv != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
I am experiencing the same since 1 or 2 weeks ago. Before I was running 12.10 (upgraded from 12.04) and empathy worked. Probably connected to this bug is the bug that evolution always asks for passphrases of several accounts. How can I dump that stupid Ubuntu accounts and get the original application based accounts? Since the introduction of the ubuntu online accounts it is broken and gets fixed after a few months. Please don't bug users with such crap alpha version software. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1072693] Re: Empathy does not connect accounts, Facebook, Google, Outlook
I am experiencing the same since 1 or 2 weeks ago. Before I was running 12.10 (upgraded from 12.04) and empathy worked. Probably connected to this bug is the bug that evolution always asks for passphrases of several accounts. How can I dump that stupid Ubuntu accounts and get the original application based accounts? Since the introduction of the ubuntu online accounts it is broken and gets fixed after a few months. Please don't bug users with such crap alpha version software. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072693 Title: Empathy does not connect accounts, Facebook, Google, Outlook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1072693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 903422] Re: Ubuntu does not work with Samsung Galaxy phones (needs update to libmtp)
I just upgraded to 12.10 and get the same error from mtp-detect: PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/903422 Title: Ubuntu does not work with Samsung Galaxy phones (needs update to libmtp) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
At runtime kill -sighup works fine without any messages in /var/log/syslog. Service reload as well. The problem seems only to occure at boot and the only message I found about this the killed by HUP signal mentioned above. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
Mine is an atom netbook mini server too. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
At runtime kill -sighup works fine without any messages in /var/log/syslog. Service reload as well. The problem seems only to occure at boot and the only message I found about this the killed by HUP signal mentioned above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
Mine is an atom netbook mini server too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995523] [NEW] squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
Public bug reported: During boot squid3 is started successfully by upstart and then killed by /etc/resolvconf/update-libc.d/squid3 but not restarted. Can be fixed by changing /etc/resolvconf/update-libc.d/squid3 to: #!/bin/sh PATH=/usr/sbin:/usr/bin:/sbin:/bin # Make squid aware of changes to resolv.conf if status squid3 | grep start/running /dev/null; then restart squid3 #reload squid3 fi This bug is related to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526 https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750 Also /etc/resolvconf/update-libc.d/squid can be deleted in precise because squid is only a transitional package which leads to an failure message in upstart. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Description changed: During boot squid3 is started successfully by upstart and then killed by /etc/resolvconf/update-libc.d/squid3 but not restarted. - Can be fixed by changing to: + Can be fixed by changing /etc/resolvconf/update-libc.d/squid3 to: #!/bin/sh PATH=/usr/sbin:/usr/bin:/sbin:/bin # Make squid aware of changes to resolv.conf if status squid3 | grep start/running /dev/null; then - restart squid3 - #reload squid3 + restart squid3 + #reload squid3 fi This bug is related to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526 https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750 Also /etc/resolvconf/update-libc.d/squid can be deleted in precise because squid is only a transitional package which leads to an failure message in upstart. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] [NEW] squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
Public bug reported: During boot squid3 is started successfully by upstart and then killed by /etc/resolvconf/update-libc.d/squid3 but not restarted. Can be fixed by changing /etc/resolvconf/update-libc.d/squid3 to: #!/bin/sh PATH=/usr/sbin:/usr/bin:/sbin:/bin # Make squid aware of changes to resolv.conf if status squid3 | grep start/running /dev/null; then restart squid3 #reload squid3 fi This bug is related to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526 https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750 Also /etc/resolvconf/update-libc.d/squid can be deleted in precise because squid is only a transitional package which leads to an failure message in upstart. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Description changed: During boot squid3 is started successfully by upstart and then killed by /etc/resolvconf/update-libc.d/squid3 but not restarted. - Can be fixed by changing to: + Can be fixed by changing /etc/resolvconf/update-libc.d/squid3 to: #!/bin/sh PATH=/usr/sbin:/usr/bin:/sbin:/bin # Make squid aware of changes to resolv.conf if status squid3 | grep start/running /dev/null; then - restart squid3 - #reload squid3 + restart squid3 + #reload squid3 fi This bug is related to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526 https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750 Also /etc/resolvconf/update-libc.d/squid can be deleted in precise because squid is only a transitional package which leads to an failure message in upstart. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
The new driver version 12-1 available from http://support.amd.com/us/Pages/AMDSupportHub.aspx finally fixed it for my notebook with HD4650. All animations and so are fast and smooth. For installation you will need to download the package from the site above. The following steps only work if you were using the fglrx before! At my system 2 additionally packages were needed: sudo apt-get install execstack dh-modaliases go to your download folder: cd Downloads generate the Debs: sh ati-driver-installer-12-1-x86.x86_64.run --buildpkg install the Debs: sudo dpkg -i fglrx*.deb -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
The new driver version 12-1 available from http://support.amd.com/us/Pages/AMDSupportHub.aspx finally fixed it for my notebook with HD4650. All animations and so are fast and smooth. For installation you will need to download the package from the site above. The following steps only work if you were using the fglrx before! At my system 2 additionally packages were needed: sudo apt-get install execstack dh-modaliases go to your download folder: cd Downloads generate the Debs: sh ati-driver-installer-12-1-x86.x86_64.run --buildpkg install the Debs: sudo dpkg -i fglrx*.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
Somewhere I read that the latest Gnome shell from Ricotz PPA will work but this is not the case. So you do not have to install it. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
Somewhere I read that the latest Gnome shell from Ricotz PPA will work but this is not the case. So you do not have to install it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
I do not have the blank screen after booting any more. So there is a progress. Still gnome shell is unusable because of poor performance and flickering. Rest is ok. Why should Canonical care about a competing desktop? I tried this Fedora 16 Live CD this week and I cannot even boot it - blank screen. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
I do not have the blank screen after booting any more. So there is a progress. Still gnome shell is unusable because of poor performance and flickering. Rest is ok. Why should Canonical care about a competing desktop? I tried this Fedora 16 Live CD this week and I cannot even boot it - blank screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 842566] Re: Libreoffice and unity integration broken.
I have this behavior always with the writer. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/842566 Title: Libreoffice and unity integration broken. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/842566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
The flickering has gone for me since I disabled some features in CCC. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
The flickering has gone for me since I disabled some features in CCC. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
The blank sceen bug after boot has gone with 11.10. Gnome shell looks good, but the screen refreshes quite often. Seems the display manger or window manager crashes and is restarted. In Unity the AMD Catalyst Control Center is not availible in Unity. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
Dont know, here it flickers a lot. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
The blank sceen bug after boot has gone with 11.10. Gnome shell looks good, but the screen refreshes quite often. Seems the display manger or window manager crashes and is restarted. In Unity the AMD Catalyst Control Center is not availible in Unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838577] Re: GNOME Shell display problems with FGLRX
Dont know, here it flickers a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
This worked for me on a configuration with fglrx installed: 1.Download the current ATI driver here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx 2. Build the driver in terminal and download directory with: sh ati-driver-installer-11-9-x86.x86_64.run --buildpkg 3. Remove the installed fglrx: sudo apt-get purge fglrx fglrx-amdcccle 4. Install the new driver packages by double clicking on the before built debs. 5. Make sure that the driver is installed: dpkg -l fglrx* 6. Restart 7. Check with: fglrxinfo Normally it is recommended to execute but I did not do: sudo aticonfig --initial This writes the xorg configuration If you wish to change back to the normal fglrx: sudo apt-get purge fglrx fglrx-amdcccle sudo apt-get install fglrx fglrx-amdcccle -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
There is no fglrx-modaliases any more. Try to choose recovery mode in Grub and then just resume. Maybe you should wait until the new fglrx is in repositories. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
This worked for me on a configuration with fglrx installed: 1.Download the current ATI driver here: http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx 2. Build the driver in terminal and download directory with: sh ati-driver-installer-11-9-x86.x86_64.run --buildpkg 3. Remove the installed fglrx: sudo apt-get purge fglrx fglrx-amdcccle 4. Install the new driver packages by double clicking on the before built debs. 5. Make sure that the driver is installed: dpkg -l fglrx* 6. Restart 7. Check with: fglrxinfo Normally it is recommended to execute but I did not do: sudo aticonfig --initial This writes the xorg configuration If you wish to change back to the normal fglrx: sudo apt-get purge fglrx fglrx-amdcccle sudo apt-get install fglrx fglrx-amdcccle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838577] Re: GNOME Shell display problems with FGLRX
There is no fglrx-modaliases any more. Try to choose recovery mode in Grub and then just resume. Maybe you should wait until the new fglrx is in repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
This is the Ubuntu fglrx driver, not the latest by AMD. With this driver Gnome shell does not work. You have to compile manually the AMD website driver and install it over an existing fglrx. Please see the wiki pages how to do this. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
This is the Ubuntu fglrx driver, not the latest by AMD. With this driver Gnome shell does not work. You have to compile manually the AMD website driver and install it over an existing fglrx. Please see the wiki pages how to do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
This only means that the fix is released, not that it is available. So far you would have to install fglrx from the ATI website manually. This means download and compile, see wiki for more information. Best is over an existing fglrx so that all the xorg stuff is right. So you should have installed version 11.9 before by additional drivers function. Just uninstall the old fglrx and double click on the new one for installing. Do the same with the control center. The earlier mentioned way to purge is not recommended by me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 838577] Re: GNOME Shell display problems with FGLRX
For me it works ok. I have got a 5750. Are you sure you installed the correct preperitary driver of the ATI web site? You probably have the open source driver running. The version should be 2:8.892 as shown in synaptics and must be enabled by xorg, means shown active in the additional drivers dialog. I just had some trouble to install the compiled drivers by the softwarecenter. Not it is installed and still cannot find the control center in unity. I have to call it manually. Dont know why. Maybe it does not work with manually installed applications. BTW Gnome Shell is still less mature that unity. A lot of functions is missing. To make it work one has to install a lot of stuff. Best is the ppa by webup8.org and follow their hints. For me I rather stay at unity. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 838577] Re: GNOME Shell display problems with FGLRX
This only means that the fix is released, not that it is available. So far you would have to install fglrx from the ATI website manually. This means download and compile, see wiki for more information. Best is over an existing fglrx so that all the xorg stuff is right. So you should have installed version 11.9 before by additional drivers function. Just uninstall the old fglrx and double click on the new one for installing. Do the same with the control center. The earlier mentioned way to purge is not recommended by me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 838577] Re: GNOME Shell display problems with FGLRX
For me it works ok. I have got a 5750. Are you sure you installed the correct preperitary driver of the ATI web site? You probably have the open source driver running. The version should be 2:8.892 as shown in synaptics and must be enabled by xorg, means shown active in the additional drivers dialog. I just had some trouble to install the compiled drivers by the softwarecenter. Not it is installed and still cannot find the control center in unity. I have to call it manually. Dont know why. Maybe it does not work with manually installed applications. BTW Gnome Shell is still less mature that unity. A lot of functions is missing. To make it work one has to install a lot of stuff. Best is the ppa by webup8.org and follow their hints. For me I rather stay at unity. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838577 Title: GNOME Shell display problems with FGLRX To manage notifications about this bug go to: https://bugs.launchpad.net/fglrx/+bug/838577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Desktop-packages] [Bug 816479] Re: UbuntuOne contacts not available after upgrade to Oneiric
This bug is not couchdb connected because it affects google stored contacts as well. Google address book in evolution will be only available in evolution if sudo killall -9 e-addressbook-factory is executed. Before it says that the address book is not available because already opened by another process. Local address books in evolution are not affected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-couchdb in Ubuntu. https://bugs.launchpad.net/bugs/816479 Title: UbuntuOne contacts not available after upgrade to Oneiric Status in “evolution-couchdb” package in Ubuntu: Confirmed Bug description: After upgrading to Oneiric a few days ago, I lost all my contacts. Initially I was affected by bug #780972 but now that bug is resolved. I check UbuntuOne and I have Contacts syncs checked. I have the evolution-couchdb packages installed. I removed my keys from gnome- keyring as per the UbuntuOne FAQ, but that didn't work either. If I click on Ubuntu One in Contacts in evoltuion, there is nothing there whereas if I go to the Ubuntu One dashboard, I have all of them listed. Original Description: After upgrading to Oneiric a few days ago, I lost all my contacts. Selecting CouchDB/Ubuntu One in evolution gives the following error message: Unable to open address book This address book cannot be opened. This either means that an incorrect URI was entered, or the server is unreachable. Detailed error message: Message did not receive a reply (timeout by message bus) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evolution-couchdb 0.5.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-6.7-generic 3.0.0-rc7 Uname: Linux 3.0.0-6-generic x86_64 Architecture: amd64 Date: Tue Jul 26 10:22:16 2011 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110425.2) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evolution-couchdb UpgradeStatus: Upgraded to oneiric on 2011-07-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-couchdb/+bug/816479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Bug 816479] Re: UbuntuOne contacts not available after upgrade to Oneiric
This bug is not couchdb connected because it affects google stored contacts as well. Google address book in evolution will be only available in evolution if sudo killall -9 e-addressbook-factory is executed. Before it says that the address book is not available because already opened by another process. Local address books in evolution are not affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/816479 Title: UbuntuOne contacts not available after upgrade to Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-couchdb/+bug/816479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 663480] Re: ATI proprietary driver (fglrx) does not provide correct EDID data
It is still a bug in Natty. I cannot change the color profile in GCM since the display is show as disconnected. Dispwin works fine. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/663480 Title: ATI proprietary driver (fglrx) does not provide correct EDID data ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 663480] Re: ATI proprietary driver (fglrx) does not provide correct EDID data
It is still a bug in Natty. I cannot change the color profile in GCM since the display is show as disconnected. Dispwin works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/663480 Title: ATI proprietary driver (fglrx) does not provide correct EDID data -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Gtg] [Question #113756]: Sync Google/GMail tasks with Getting Things Gnome
Question #113756 on Getting Things GNOME! changed: https://answers.launchpad.net/gtg/+question/113756 Steffen Sindzinski posted a new comment: Any progress in google task integration! Since remember the milk wants money on android I don't have a way to sync my taks between gnome and android yet and this feature would be great. Thanks! -- You received this question notification because you are a member of Gtg developers, which is an answer contact for Getting Things GNOME!. ___ Mailing list: https://launchpad.net/~gtg Post to : gtg@lists.launchpad.net Unsubscribe : https://launchpad.net/~gtg More help : https://help.launchpad.net/ListHelp
[Bug 661593] Re: Samsung R522 Intel Core 2 Duo 2.0 with ATI 4560 everheats running Maverick Live CD desktop 64
The application will be able to access Launchpad on your behalf for reading and changing anything, including private data. Apport collects potentially sensitive data, such as core dumps, stack traces, and log files. They can contain passwords, credit card numbers, serial numbers, and other private material. How can I check the private data before uploading? Since this is a productive machine I'm not allowed to upload this unchecked. BTW /var/crash does not exist. Greetings, Steffen -- Samsung R522 Intel Core 2 Duo 2.0 with ATI 4560 everheats running Maverick Live CD desktop 64 https://bugs.launchpad.net/bugs/661593 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 661593] [NEW] Samsung R522 Intel Core 2 Duo 2.0 with ATI 4560 everheats running Maverick Live CD desktop 64
Public bug reported: Hi, I tried to install Maverick 10.10 from Live CD 64 bit on my Samsung R522. During installation the notebook overheats and emergency shuts down. I managed to install let the notebook cool down and choosed direct installation without the try out option. But the running system still overheated! Even in idle (cpu usage around 4-10%) the processors temp incresed after a period of time to emergency shut down at 90 degrees Celsius! I checked all, the processor is idle and running on low frequency, fans are running. The idle temp was in the upper 60 degrees! Same time on Windows Vista everything was going well, idle temp around upper 30 degrees. I tried out to install the fglrx graphics driver from repository and now the idle temp is in the 50th. While working around 70-80. But still much hotter than Windows while having a lower CPU usage than Windows. Why it is still so hot? It also seems that the fans are running at lower speed at given temperature than in Windows. Could this be the problem? Running in the 80th reduces my processors lifetime. The standard driver (without installing fglrx) lets the system overheat and could damage the notebook. Even at full speed it should not overheat! ** Affects: ubuntu Importance: Undecided Status: New -- Samsung R522 Intel Core 2 Duo 2.0 with ATI 4560 everheats running Maverick Live CD desktop 64 https://bugs.launchpad.net/bugs/661593 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 581707] Re: quickly release failed with python stack trace
Is there a fix or workaround? I cannot release my new version. -- quickly release failed with python stack trace https://bugs.launchpad.net/bugs/581707 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 390875] Re: gnome-settings-daemon exits without error message
Same for me, quite annoying. New installed lucid with fglrx from repository, encrypted home. -- gnome-settings-daemon exits without error message https://bugs.launchpad.net/bugs/390875 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 390875] Re: gnome-settings-daemon exits without error message
Same for me, quite annoying. New installed lucid with fglrx from repository, encrypted home. -- gnome-settings-daemon exits without error message https://bugs.launchpad.net/bugs/390875 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 582879] [NEW] Merge database does not work
Public bug reported: Binary package hint: f-spot I want to merge the db of my travel notebook with the db of my home notebook. I'm using a backup of my home directory. If I select the db in my backup directory, choose any option (only new, only singe imports,...) and press ok the import starts. After a while a dialog appears and ask for the path to the photos. It says that the original path does not exists any more. I select the same relative path in my backup. But the dialog appears and appears. Then I have to kill the process. If I copy all the pictures manually from the backup into the pictures folder the same happens no matter which of the options I'm using. Thanks, Steffen ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- Merge database does not work https://bugs.launchpad.net/bugs/582879 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 487191] Re: F-spot leaks huge amount of memory while importing pictures
I know this bug is just for one file but on normal computers like a dual core with 2 gig RAM an import of 15.000 photos is not possible because all available RAM and swap is eaten by the import. I think this is not necessary because during the first step of the import photos are already imported to the photo folder and added to the database. After this the program starts to ask which photos should be imported. A better process would be just to load the thumbs but not to copy the photos and not to add it to the database. This would accelerate the import. -- F-spot leaks huge amount of memory while importing pictures https://bugs.launchpad.net/bugs/487191 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 582879] [NEW] Merge database does not work
Public bug reported: Binary package hint: f-spot I want to merge the db of my travel notebook with the db of my home notebook. I'm using a backup of my home directory. If I select the db in my backup directory, choose any option (only new, only singe imports,...) and press ok the import starts. After a while a dialog appears and ask for the path to the photos. It says that the original path does not exists any more. I select the same relative path in my backup. But the dialog appears and appears. Then I have to kill the process. If I copy all the pictures manually from the backup into the pictures folder the same happens no matter which of the options I'm using. Thanks, Steffen ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- Merge database does not work https://bugs.launchpad.net/bugs/582879 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 487191] Re: F-spot leaks huge amount of memory while importing pictures
I know this bug is just for one file but on normal computers like a dual core with 2 gig RAM an import of 15.000 photos is not possible because all available RAM and swap is eaten by the import. I think this is not necessary because during the first step of the import photos are already imported to the photo folder and added to the database. After this the program starts to ask which photos should be imported. A better process would be just to load the thumbs but not to copy the photos and not to add it to the database. This would accelerate the import. -- F-spot leaks huge amount of memory while importing pictures https://bugs.launchpad.net/bugs/487191 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
