[Bug 1705156] Re: gnome-shell interface shows up extremely scaled up
For the record, this just happened to me on a *fresh* install of Ubuntu 18.04. The first thing I did after system installed months ago was to install Unity from repositories (and set lightdm as the default greeter). Unity may not be the default anymore in 18.04 but it runs and looks great. Today I needed to test Gnome Shell. So I logged out, and in the greeter selected "Ubuntu" instead of pre-selected "Unity (Default)". And that *insane* zoom up happened. Same as described by OP. Logging out and back into Unity everything is OK. Also tried "Ubuntu on Wayland)" and same super super zoom. Super+Alt+8 fixes the zoom. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705156 Title: gnome-shell interface shows up extremely scaled up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1705156] Re: gnome-shell interface shows up extremely scaled up
For the record, this just happened to me on a *fresh* install of Ubuntu 18.04. The first thing I did after system installed months ago was to install Unity from repositories (and set lightdm as the default greeter). Unity may not be the default anymore in 18.04 but it runs and looks great. Today I needed to test Gnome Shell. So I logged out, and in the greeter selected "Ubuntu (default)" instead of pre-selected "Ubuntu (Unity)". And that *insane* zoom up happened. Same as described by OP. Logging out and back into Unity everything is OK. Also tried "Ubuntu (default on Wayland)" and same super zoom -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1705156 Title: gnome-shell interface shows up extremely scaled up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1705156/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1122613] Re: XDG Base Directory Specification environment variables aren't set by default
This is not a bug, as the standard specification linked in the description clearly defines what defaults values should be used if the environment vars are empty or not set. So there is no need to set the values unless you want to change the default ones, and it would be redundant to set them to their default. ** Changed in: xdg-user-dirs (Ubuntu) Status: Confirmed => Invalid ** Changed in: xdg-user-dirs (Debian) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/1122613 Title: XDG Base Directory Specification environment variables aren't set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-user-dirs/+bug/1122613/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 378783] Re: xdg-open *.desktop opens text editor
@Tom #7: gnome-open was deprecated a long time ago, xdg-open now uses gvfs-open. Upstream bug report is https://bugzilla.gnome.org/show_bug.cgi?id=343896 ** Bug watch added: GNOME Bug Tracker #343896 https://bugzilla.gnome.org/show_bug.cgi?id=343896 ** Package changed: xdg-utils (Ubuntu) = gvfs (Ubuntu) ** Also affects: gvfs via https://bugzilla.gnome.org/show_bug.cgi?id=343896 Importance: Unknown Status: Unknown ** Bug watch removed: Wine Bugzilla #19702 http://bugs.winehq.org/show_bug.cgi?id=19702 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/378783 Title: xdg-open *.desktop opens text editor To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/378783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 864615] Re: Thumbnailers are missing in gconf
Shouldn't this import be the other way around? AFAIK, Gnome 3 uses /usr/share/thumbnailers/*.thumbnailer files to implement external handlers, NOT gsettings. The gconf2 was the Gnome 2 (ie, Natty and before) way of registering external thumbnailers. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/864615 Title: Thumbnailers are missing in gconf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/864615/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 562476] Re: x-www-browser, sensible-browser and gnome-www-browser don't use the default browser
@Thibault: xdg-open, for sure, and for 2 main reasons: - xdg-open is more portable: it chooses the most appropriate open command for your system, be it Gnome, KDE, LXDE, XFCE, etc, while gnome- open works only in gnome. In fact, in Gnome systems xdg-open used to end up calling gnome-open. So let it choose the suitable opener for you. - gnome-open is deprecated, and was replaced by gvfs-open. A quick googling reveals https://live.gnome.org/LibgnomeMustDie , and also https://developer.pidgin.im/ticket/15556 offers some insight. xdg-open was updated a long time ago to use gvfs-open if it was available, and fallback to gnome-open for (really) old systems Worth note that gvfs-open (and thereby xdg-open too) uses the xdg mime database system to choose an application based on mime-type handlers, which is the system used by Preferred Applications, so it respects the *user* preferences. ** Bug watch added: Pidgin Trac #15556 http://developer.pidgin.im/ticket/15556 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/562476 Title: x-www-browser, sensible-browser and gnome-www-browser don't use the default browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/562476/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] Re: Brasero calculates wrong checksum after burn ISO to CD
** This bug is no longer a duplicate of bug 367037 Error while burning - some files may be corrupted on the disc -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/385540 Title: Brasero calculates wrong checksum after burn ISO to CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/385540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 594674] Re: Trash is not shown on --bind mounted filesystems
My 2 cents for this issue: - It also happens with tmpfs mounts. I have tmpfs /tmp tmpfs defaults,nodev,nosuid,mode=1777 0 0 in my /etc/fstab and nautilus also trash files there just fine (creating and moving to /tmp/.Trash-1000), but fails to add that particular trash to the global list of trash://. So this is not only a problem with mount --bind - trash-cli package (a very handy softaware that manages trashcan) correctly list all such trashes (both mount --bind and tmpsf), regardless if files were deleted via nautilus or via trash-put command. So nautilus bug is not about trashing these files, it does this correctly, it's only about listing all available trashcans (one from each filesystem) Hope this helps narrowing the problem down -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/594674 Title: Trash is not shown on --bind mounted filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/594674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 594674] Re: Trash is not shown on --bind mounted filesystems
@Sebastien: IMHO disabling trash for those mounts (and also for *all* devices outside $HOME and /media) is overkill. Ok, it is better than current behavior, but the best approach would be to support those (already created and populated) per-device trashcans and list them when the user clicks on the trash. If trash-cli can, why can't Nautilus? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/594674 Title: Trash is not shown on --bind mounted filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/594674/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 882040] Re: should let users enable or disable suspend and hibernate
How viable is for Ubuntu to create a package available in Software Center that patches gnome's GUI and/or polkit (whatever is required) to re-enable hibernation? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/882040 Title: should let users enable or disable suspend and hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34629] Re: Left-click clears PRIMARY buffer selection (Copy-paste with middle-button/mouse wheel fails)
I have this bug too (on Maverick) My 2 cents: - gedit clears the primary *only* if the selection was made on gedit itself! (yes, this seems absurd, i know) Steps to reproduce: - Select something in Firefox (double or triple click this very line). Alt+Tab to gedit. Middle-click. Pastes fine - Left click another part of the text in gedit. Middle-click. Pastes fine - Select something in gedit (double or triple click) Alt+Tab to firefox. Middle-click. Pastes fine - Alt+Tab back to gedit. Middle-click anywhere (without left-clicking!). Pastes fine - Left click another part of the text in gedit. Middle-click. PASTE FAILS - Alt+tab to firefox. Middle-click. PASTE FAILS - Select something in Firefox (double or triple click this very line). Alt+Tab to gedit. - Use keyboard arrow keys to move cursor somewhere else. Middle-click. Pastes fine - Select something in gedit. Use keyboard arrow keys to move cursor somewhere else. Middle-click. PASTE FAILS (fails also if you use CTRL+Z or any key that moves the text cursor to another place) So it looks like the primary is cleared if text cursor in gedit moves (by left-click or arrow keys or any other way) and the selection was made in gedit itself. Is this behavior the same bug or another, new one? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/34629 Title: Left-click clears PRIMARY buffer selection (Copy-paste with middle- button/mouse wheel fails) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/34629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 642792] Re: ALT+PrtSc not recognised: breaks built-in screenshot function
Florian Sievers (#31) is right: in a clean Maverick install, 'cat /proc/sys/kernel/sysrq' (or 'sudo sysctl -a | grep kernel.sysrq') shows kernel.sysrq=0 , but in fact sysrq's are enabled (and eating up Alt+PrtScn). If i set it as 'sudo sysctl -w kernel.sysrq=0', supposedly it wouldn't change anything, since its already 0, but yet it disables sysrqs and allows me to take windowshots again. So currently this is really a mess. If this is fixed for Natty, Oneric, great. But for Maverick it is not, so please at least issue an SRU to fix that! It is *very* annoying, and newcomers and novice users will find this *very* frustrating, to say the least. In Lucid, both worlds were happy: Alt+PrnScr alone took windowshots, and Alt+PrnScr+somekey triggered Sysrqs. Maverick *should* have the same behaviour. Also, as spoken here several times: this is expected even from Windows users. Sysrq's can also be triggered with Right Alt (AltGr here) + PrnScr. Taking windowshots is *far* more common then Sysrqs (meant for emergencies only). Those who know what a sysrq is can easily workaround this. Most of screenshoters (=regular users) can not. Please revert to the expected behavior! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/642792 Title: ALT+PrtSc not recognised: breaks built-in screenshot function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/642792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 367037] Re: Error while burning - some files may be corrupted on the disc
@lopthopman (#26): I just said that you are experiencing a different issue than what is reported here. This bug here is for false alarms, when copy is OK but Brasero calculares checksum incorrectly and thus reports burning errors. If you are actually getting coasters, this should be reported in a different bug (new or already existing one) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/367037 Title: Error while burning - some files may be corrupted on the disc To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/367037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
Any chance this can be cherry-picked to maverick backports or updates? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 739790] Re: cannot access trash:// computer:// network://
@Aleck: this is NOT the same bug. That bug happened when nautilus migrated from GnomeVFS to gvfs/GIO. And this one is about something else: @Nikolaus: this happened because gnome migrated (again) the settings for opening URIs (http:// , ftp:// , magnet:, mailto:, etc). Back in Maverick, gnome stored default launchers at gconf settings. Now, to make it similar / consistent with file handlers, it uses xdg mime database. The problem is Ubuntu didn't provide default settings in the new method for some URIs like the ones you mentioned (trash://, computer:// etc) The workaround of editing /usr/share/applications/mimeinfo.cache works, but that is not the proper place to fix that. That file is meant to be automatically generated when new applications are installed in the system. The place you should edit is: For system-wide change: /usr/share/applications/defaults.list For your user only: /home/your user /.local/share/applications/defaults.list (also, you may check /usr/share/applications/mimeapps.list and /home/your user /.local/share/applications/mimeapps.list) In next version, Ubuntu will (hopefully) ships with an updated defaults.list that already includes all URIs -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/739790 Title: cannot access trash:// computer:// network:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/739790/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
** Patch added: Patch gvfs-open so exit code = 1 when it fails to open any file https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237738/+files/0001-gvfs-open-655470.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
Question: if this patch gets approved and merged upstream, what should i do to make it cherry-picked all the way to Maverick ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
Updated patch, with cosmetic changes (spacing, line breaks, commit message) ** Patch added: Patch gvfs-open so exit code = 1 when it fails to open any file https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237872/+files/0001-gvfs-open-655470.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
** Patch removed: Patch gvfs-open so exit code = 1 when it fails to open any file https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237738/+files/0001-gvfs-open-655470.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] [NEW] gvfs-open exit code is 0 when file is not found and no default application is registred
Public bug reported: gvfs-open exits with error code 0 (success) even when there is error. The following conditions should exit with error code 0: - File is not found - File is found, but default application for opening it is not registred Examples: $ gvfs-open nofile.txt || echo NOT FOUND! gvfs-open: file:///home/rodrigo/nofile.txt: error opening location: Error stating file '/home/rodrigo/nofile.txt': No such file or directory $ touch test.mdb ; gvfs-open nofile.txt || echo NO ASSOCIATION! ; rm test.mdb gvfs-open: file:///home/rodrigo/nofile.txt: error opening location: Error stating file '/home/rodrigo/nofile.txt': No such file or directory In both situations exit code was 0, meaning success, even when gvfs- open was clearly NOT successful. This makes gvfs-open hard to use in scripts. And the problem is even worse considering gvfs-open is used by xdg-open A quick look at source code shows that it has a hardcoded return 0 in main() function. The open() function is static void. Both could easily be changed so open would be static int open(...), set a proper return code, and main would test for it. Using Maverick 10.10 64bits, gvfs 1.6.4-0ubuntu1.1 ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 816804] Re: gvfs-open exit code is 0 when file is not found and no default application is registred
** Bug watch added: GNOME Bug Tracker #655470 https://bugzilla.gnome.org/show_bug.cgi?id=655470 ** Also affects: gvfs via https://bugzilla.gnome.org/show_bug.cgi?id=655470 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/816804 Title: gvfs-open exit code is 0 when file is not found and no default application is registred To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/816804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 367037] Re: Error while burning - some files may be corrupted on the disc
@lopthman: this bug is about a false alarm, not actual burning problem. Also, for developers, my comment on a duplicate bug may help find the answer: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/385540/comments/2 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/367037 Title: Error while burning - some files may be corrupted on the disc To manage notifications about this bug go to: https://bugs.launchpad.net/brasero/+bug/367037/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 702093] Re: Root Nautilus does not access Trash
Very annoying bug, and its there for at least 9.04 One could still purge the files by manually deleting the contents or /root/.local/share/.Trash But restoring the files requires one to manually read the info/xxx.trashinfo contents to know the original location of the trashed file. Why cant the root use / empty / restore the trash as any normal user? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. https://bugs.launchpad.net/bugs/702093 Title: Root Nautilus does not access Trash -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 422012] Re: Protected files hidden by Trash
8 months since bug was confirmed. Any news on it? By the way, where ccan i find the rationale / specification on this expunged folder? Is it for big files, other-users files, both, none, something else? Last but not least: shouldnt these files be deleted on reboot? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/422012 Title: Protected files hidden by Trash -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 545107] Re: Help button doesn't launch help
It is still present on 10.10 Maverick. If upstream was fixed almost 1 year ago, shouldnt Update Manager have already download the fix / updated package? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. https://bugs.launchpad.net/bugs/545107 Title: Help button doesn't launch help -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] [NEW] Brasero calculates wrong checksum after burn ISO to CD
Public bug reported: Binary package hint: brasero After burning a CD from an ISO file, Brasero reports an error saying checksum from ISO file and burned CD do not match. (Some files may be corrupted on the disc). However, CD is fine and all files were burned correctly. I did a manual verification using md5sum on both the ISO and on the burned CD, and they DO match. Steps to reproduce: - In Nautilus, right-click an .ISO file (i used ubuntu-9.04-desktop-i386.iso) and select Write to Disc. - Click Burn After recording, it says Some files may be corrupted on the disc. Opening up the logfile, near the end theres the line that triggered the error: BraseroChecksumImage Setting new checksum (type = 2) 2602036235674bdd37d297dadd7547dd (66fa77789c7b8ff63130e5d5a272d67b before) Steps to Verify: - Check the ISO hash: md5sum ubuntu-9.04-desktop-i386.iso ( it says 66fa77789c7b8ff63130e5d5a272d67b, same checksum as in Ubuntu documentation https://help.ubuntu.com/community/UbuntuHashes ) - Check the CD hash: md5sum /media/cdrom (again, 66fa77789c7b8ff63130e5d5a272d67b) - Create ISO from CD using Brasero, and then check md5sum: 66fa77789c7b8ff63130e5d5a272d67b So Brasero, for some reason, is not calculating the burned CD checksum correctly. I tried with the same ISO twice, and then with another ISO (the one i am attaching). The 3 discs were OK but in all Brasero reported this error. PS: This is my 1st bug report, im new to Ubuntu, so I apologize theres anything incorrect in the report format. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/brasero NonfreeKernelModules: nvidia Package: brasero 2.26.1-0ubuntu1 ProcEnviron: LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: brasero Uname: Linux 2.6.28-11-generic i686 ** Affects: brasero (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 -- Brasero calculates wrong checksum after burn ISO to CD https://bugs.launchpad.net/bugs/385540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] Re: Brasero calculates wrong checksum after burn ISO to CD
** Attachment added: brasero-session.log http://launchpadlibrarian.net/27726485/brasero-session.log ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/27726486/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/27726487/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/27726488/ProcStatus.txt -- Brasero calculates wrong checksum after burn ISO to CD https://bugs.launchpad.net/bugs/385540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] Re: Brasero calculates wrong checksum after burn ISO to CD
After studying the log and doing some tests, i think ive spotted the error: Brasero is passing the wrong number of sectors to the readom command (that looks like its the one brasero uses to read the burned cd to calculate the checksum). These log lines should says it all (some lines were omitted for the sake of clarity): BraseroChecksumImage Starting checksuming file /dados/Install/Linux/ubuntu-9.04-desktop-i386.iso (size = 732909568) BraseroChecksumImage Setting new checksum (type = 2) 66fa77789c7b8ff63130e5d5a272d67b ( before) BraseroWodim stdout: Track 01: data 698 MB BraseroWodim stdout: Total size: 802 MB (79:31.54) = 357866 sectors BraseroWodim stdout: Lout start: 803 MB (79:33/41) = 357866 sectors BraseroWodim stdout: Current Secsize: 2048 BraseroWodim stdout: Blocks total: 359846 Blocks current: 359846 Blocks remaining: 1980 BraseroWodim stdout: Track 01: 698 of 698 MB written (fifo 100%) [buf 100%] 8.1x. BraseroWodim stdout: Track 01: Total bytes read/written: 732909568/732909568 (357866 sectors). So far so good: ISO checksum and size are correct, and 732909568 bytes / 2048 b/s = 357866 sectors. Media has 359846 sectors in total, so 359846 - 357866 = 1980 sectors wont be used. Track data is 698 MB (698.95 actually), and they are all sucessfully written to disc. Then surprisingly, a few lines latter brasero says: BraseroChecksumImage Starting checksum generation live (size = 732905472) BraseroReadom reading 1 from sector 0 to 357864 BraseroReadom got varg: readom dev=/dev/sr0 -nocorr -noerror -sectors=0-357864 -f=- BraseroReadom stderr: Capacity: 357866 Blocks = 715732 kBytes = 698 MBytes = 732 prMB BraseroReadom stderr: end:357864 BraseroReadom stderr: addr: 357864 BraseroReadom stderr: Read 715728.00 kB at 5110.6 kB/sec. BraseroChecksumImage Setting new checksum (type = 2) 2602036235674bdd37d297dadd7547dd (66fa77789c7b8ff63130e5d5a272d67b before) size = 732905472 Why 732905472 ? Thats 4096 bytes less than the ISO image! Thats 357864 sectors, 2 less than it should. And, since only a partial data was read from CD, checksum was obvioulsy different then original I did a few tests with readom, using the same parameter template as used by brasero: readom dev=/dev/sr0 -nocorr -noerror -sectors=0-357864 -f=- | md5sum 2602036235674bdd37d297dadd7547dd - readom dev=/dev/sr0 -nocorr -noerror -sectors=0-357866 -f=- | md5sum 66fa77789c7b8ff63130e5d5a272d67b - Both values matches the ones found in the log. So md5sum of burned CD is correctly calculated on an incorrect, 4K smaller data. Thats why brasero says checksums do not match. Looks like bug has nothing to do with wodin, readom, or md5 calculation. Seems to be a brasero issue iself, passing a wrong parameter. Shoudnt it use the actual ISO size instead ? Last but not least, ISO was read from an NTFS partition that was mounted in /dados. Does it matter? Hope this helps! PS: Here the log for this example. Previous post log is from another ISO (but had the same error, brasero passed 2 sectors less then actual iso size) ** Attachment added: brasero-session.log http://launchpadlibrarian.net/27729895/brasero-session.log -- Brasero calculates wrong checksum after burn ISO to CD https://bugs.launchpad.net/bugs/385540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] Re: Brasero calculates wrong checksum after burn ISO to CD
** Branch linked: lp:~ubuntu-desktop/brasero/ubuntu -- Brasero calculates wrong checksum after burn ISO to CD https://bugs.launchpad.net/bugs/385540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 385540] Re: Brasero calculates wrong checksum after burn ISO to CD
** Branch unlinked: lp:~ubuntu-desktop/brasero/ubuntu -- Brasero calculates wrong checksum after burn ISO to CD https://bugs.launchpad.net/bugs/385540 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 371065] Re: system monitor crazy speed update
*** This bug is a duplicate of bug 205362 *** https://bugs.launchpad.net/bugs/205362 ** This bug has been marked a duplicate of bug 205362 system monitor update interval is not in seconds -- system monitor crazy speed update https://bugs.launchpad.net/bugs/371065 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 205362] Re: system monitor update interval is not in seconds
Some hints that might help debugging: The FIRST and SECOND refreshes happens at the correct interval. Steps to reproduce: - Open up System Monitor and switch to Resource tab - Set the interval to 10,00 (using the buttons, not keyboard - theres another bug associated with keyboard input) - Click Close (the dialog box) - Note that actual refresh now is 1s - Close the program - Open it again and just watch - The FIRST refresh takes 10 seconds to happen. You can notice that by CPU % box change - The SECOND refresh takes another 10 seconds to happen. You can notice that by CPU % box change - The THIRD and all subsequent refreshes now take only 1s The offset is confirmed to be 10 times faster. This behavior might be caused by a locale misreading of textbox value. In some locales (like Brazil), the decimal placeholder is , (comma), NOT . (period). So 10,00 = 10 and 10.00 = 1000. As in the US its the opposite, a value input of 10,00 in a PT-BR locale computer may be read and erroneously converted by internal functions as 1000, according to EN-US locale. And, as max value of this field is 99, maybe it is converting all values above 100 to MILLISECONDS instead of seconds, thus resulting in 1000 milliseconds = 1 second. So the problem may be just the software is unaware and not respecting system locale. Its a wild guess, but who knows ? My 2 cents... -- system monitor update interval is not in seconds https://bugs.launchpad.net/bugs/205362 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 205362] Re: system monitor update interval is not in seconds
Question: as this problem was already forwarded / upstreamed, should i double-post my comments at bugzilla too ? Im not sure how the process works... I dont have a bugzilla account, and even if i had, im not sure if double-posting would be the correct procedure... but i also dont like to post comments at the wrong places, as they maybe be unnoticed... -- system monitor update interval is not in seconds https://bugs.launchpad.net/bugs/205362 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 205362] Re: system monitor update interval is not in seconds
Last but not least, this bug seems to be closely related to #93847 and its various duplicates... https://bugs.launchpad.net/ubuntu/+source/gnome-system- monitor/+bug/93847 Excessive CPU usage by Gnome System Monitor In fact, all those bugs may be just a symptom of this one: a refresh 10 times faster causes a HEAVY cpu usage. Is there any way to link all these bugs with this one ? If not as duplicates, at least as related bugs ? -- system monitor update interval is not in seconds https://bugs.launchpad.net/bugs/205362 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 219548] Re: Xorg constant 70% CPU load
*** This bug is a duplicate of bug 205362 *** https://bugs.launchpad.net/bugs/205362 ** This bug is no longer a duplicate of bug 93847 Excessive CPU usage by Gnome System Monitor ** This bug has been marked a duplicate of bug 205362 system monitor update interval is not in seconds -- Xorg constant 70% CPU load https://bugs.launchpad.net/bugs/219548 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 280693] Re: system monitor consumes a lot
*** This bug is a duplicate of bug 205362 *** https://bugs.launchpad.net/bugs/205362 ** This bug is no longer a duplicate of bug 93847 Excessive CPU usage by Gnome System Monitor ** This bug has been marked a duplicate of bug 205362 system monitor update interval is not in seconds -- system monitor consumes a lot https://bugs.launchpad.net/bugs/280693 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 93847] Re: Excessive CPU usage by Gnome System Monitor
*** This bug is a duplicate of bug 205362 *** https://bugs.launchpad.net/bugs/205362 ** This bug has been marked a duplicate of bug 205362 system monitor update interval is not in seconds -- Excessive CPU usage by Gnome System Monitor https://bugs.launchpad.net/bugs/93847 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
