[Bug 1900429] Re: [snap] Unable to access files owned by another user
In my case, a docker-based firmware build process produces a update package (owned by root, for some reason), which I upload to a target via a web-interface. Sure, I can change the owner of the files but still, this used to work and it doesn't now. Let me turn the question around. What is the use-case for prohibiting access to files in the user's home directory, which are readable by the user based on good old Unix filesystem permissions? Devising a completely parallel access policy based on arbitrary and invisible rules seems utterly stupid to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900429 Title: [snap] Unable to access files owned by another user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900429] [NEW] [snap] Unable to access files owned by another user
Public bug reported: The chromium snap cannot access files in my $HOME that have a different owner, even though the files are world-readable. ** Affects: chromium-browser (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/1900429 Title: [snap] Unable to access files owned by another user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746955] [NEW] gcc-avr installs libcc1 in /usr/lib, causing package conflicts
Public bug reported: gcc-avr packages for artful and bionic includes the files /usr/lib/libcc1.* which probably isn't correct (I suspect they should be in the target specific path, if anywhere) and may conflict with other gcc packages. It specifically conflicts with the "GNU Arm Embedded Toolchain" PPA package, see https://bugs.launchpad.net/gcc-arm- embedded/+bug/1745143 . Packages for <= zesty do not include these files at all. ** Affects: gcc-avr (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/1746955 Title: gcc-avr installs libcc1 in /usr/lib, causing package conflicts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-avr/+bug/1746955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688920] Re: INFO: task systemd-udevd:326 blocked for more than 120 seconds.
This consistently happens when I use usb-creator. I've tried the lubuntu 17.10 image and the ubuntu 17.10 image, on several USB sticks. Usb- creator finally reports success, but the resulting USB stick FAILS verification (both in the installer and manually by comparing md5sums). ** Also affects: usb-creator (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/1688920 Title: INFO: task systemd-udevd:326 blocked for more than 120 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1688920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688920] Re: INFO: task systemd-udevd:326 blocked for more than 120 seconds.
By the way, this was on an up to date 17.10, kernel 4.13.0-17-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688920 Title: INFO: task systemd-udevd:326 blocked for more than 120 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1688920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1688920] Re: INFO: task systemd-udevd:326 blocked for more than 120 seconds.
I got the same dmesg output when using Startup Disk Creator to write an (L)ubuntu ISO image to a USB stick. After a very long time, and three such messages in the log, the disk creator finally claimed that it was complete. I'm not confident that the installation medium is actually OK, will try it shortly. Details of the USB stick I used: [12274.016048] usb 3-1.4: new high-speed USB device number 10 using xhci_hcd [12274.142013] usb 3-1.4: New USB device found, idVendor=0951, idProduct=1665 [12274.142018] usb 3-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [12274.142021] usb 3-1.4: Product: DataTraveler 2.0 [12274.142024] usb 3-1.4: Manufacturer: Kingston [12274.142027] usb 3-1.4: SerialNumber: 50E549C20210BE8059BC09A9 [12274.167999] usb-storage 3-1.4:1.0: USB Mass Storage device detected [12274.168534] scsi host3: usb-storage 3-1.4:1.0 [12275.275617] scsi 3:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 6 [12275.276767] sd 3:0:0:0: Attached scsi generic sg1 type 0 [12276.083697] sd 3:0:0:0: [sda] 15335424 512-byte logical blocks: (7.85 GB/7.31 GiB) [12276.084529] sd 3:0:0:0: [sda] Write Protect is off [12276.084547] sd 3:0:0:0: [sda] Mode Sense: 23 00 00 00 [12276.085363] sd 3:0:0:0: [sda] No Caching mode page found [12276.085386] sd 3:0:0:0: [sda] Assuming drive cache: write through [12276.127850] sda: sda1 [12276.131198] sd 3:0:0:0: [sda] Attached SCSI removable disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1688920 Title: INFO: task systemd-udevd:326 blocked for more than 120 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1688920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726124] Re: DNS domain search paths not updated when VPN started
BTW, the long timeout you see on short name lookup failures is most likely due to LLMNR being on by default. I think this is insane and I always switch it off in /etc/systemd/resolved.conf . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726124] Re: DNS domain search paths not updated when VPN started
Paul Smith, what you describe is information leakage and shouldn't IMHO work as you say by default. Consider that I'm connected to a corporate network and have an (untrusted) VPN active which I only want to use to access resources on its network (never-default: yes). Then by having the resolver adding the domain of the VPN network to short name lookups could leak those local names to the remote VPN (depending on the order the lookups are performed in) and potentially allow the untrusted network to take over internal services that are accessed using short names. This could happen by mistake also (such as setting "mail" as your smtp server if the remote network uses the same name). I don't think the order of the lookups can be controlled to prevent this, for example what should determine the order when you have to VPN active? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726124] Re: DNS domain search paths not updated when VPN started
to->two -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722759] [NEW] Package missing gemspec file
Public bug reported: The gemspec file is missing from the package, causing packages that depend on ruby-underscore-rails to fail on install (notably "gitlab"). Manually adding the file from https://github.com/rweng/underscore-rails/blob/v1.8.2/underscore-rails.gemspec as /usr/share/rubygems-integration/all/specifications/underscore-rails-1.8.2.gemspec (with the files hardcoded instead of using git ls-files), the package gitlab installs successfully. ** Affects: gitlab (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-underscore-rails (Ubuntu) Importance: Undecided Status: New ** Also affects: gitlab (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/1722759 Title: Package missing gemspec file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitlab/+bug/1722759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694331] Re: "internal error" popup on login
Christopher, I have since upgraded that Dell Precision to 17.04 and while I still often get the error popup on that computer I cannot confirm that it is actually Xorg that crashed, because now that I looked, the crash popup on 17.04 today was about some unrelated software (unity-settings-something) so I can't really be sure if I have ever seen Xorg crash on 17.04. It used to be Xorg when the Dell computer had 16.10, though. The UX32VD that still runs 16.10 continues to show the Xorg crash from time to time (but not nearly at every boot). Also I checked with my co-workers and those (2) who run 16.10 all regularly see an error popup but none can verify that it's still actually about Xorg (it happens frequently enough that no-one bothers to look anymore). A co-worker who's still on 16.04 says he hasn't seen the error. So in summary I can only definitely say that 16.10 shows that Xorg crash and that it has happened on more or less every computer I or my co- workers have used with 16.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694331 Title: "internal error" popup on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426596] Re: I get an "error report" popup on log-in
Reported as Bug 1694331. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426596 Title: I get an "error report" popup on log-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694331] [NEW] "internal error" popup on login
Public bug reported: Sometimes (not very often), Ubuntu shows an error popup immediately after login (after power-on) that says Xorg has crashed. No other ill effects have been noticed, everything works normally after that. The automatic error reporting does not go through because of "UnreportableReason: Invalid core dump: BFD: Warning /tmp/apport_core_5n7s8i3d is truncated: expected core file size >= 40902656, found: 21037056." I was asked by Christopher M. Penalver in Bug 1426596 to submit a new bug using "ubuntu-bug xorg" when the error appeared. This is that report, although the computer I used now to generate the report is not the same as I mentioned in the original bug (I've seen the same issue on more or less all computers I've used and IIRC from at least 16.04 to 17.04). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-53.56-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon May 29 22:31:18 2017 DistUpgraded: 2017-04-15 01:32:04,429 DEBUG /openCache(), new cache size 85680 DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-52-generic, x86_64: installed bbswitch, 0.8, 4.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1507] InstallationDate: Installed on 2014-04-18 (1137 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-53-generic.efi.signed root=UUID=959fa127-2d15-48a5-9fa0-70f918fab2ad ro rootflags=subvol=@ quiet splash pcie_aspm=force nmi_watchdog=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2017-04-14 (44 days ago) dmi.bios.date: 01/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.214:bd01/29/2013:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Mon May 29 22:28:30 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694331 Title: "internal error" popup on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1694331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426596] Re: I get an "error report" popup on log-in
This still happens from time to time on a fresh install of 16.10 on a Dell Precision 5520. So x86_64. Apport says it's unreportable because the core file is truncated. ** Changed in: xorg (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426596 Title: I get an "error report" popup on log-in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1426596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568368] Re: Misleading ellipsis in "Restart now..."
I'm pretty sure that at some point in previous releases, the normal system Shut down dialog has been shown after clicking "Reboot now..." so I could choose to shut down instead of reboot. Usually, I defer rebooting until I anyway want to shut down, so "Shut down" is the normal choice for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568368 Title: Misleading ellipsis in "Restart now..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1568368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640717] [NEW] Software Updater input events go to the wrong control
Public bug reported: When Software Updater starts, the "Details of updates" section only covers half the window's height, even though the "Technical description" section is collapsed. Refer to attached image #1. If I expand then collapse "Technical description", the "Details of updates section" restores to normal look, as in attached image #2. However, the lower part of the section (below the selected row in image) is not functional and does not respond to click, scroll or any other mouse activity. Input events instead go to the hidden "Technical description" section, for example you can change from its "Description" tab to its "Changes" tab by clicking on the checkbox two rows down from the selected one in the "Details of updates" section. Also the mouse pointer changes to a text pointer in the area that would have been covered by the text box if the "Technical description" section had been expanded (as in image #3). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: update-manager 1:16.10.7 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 10 08:22:32 2016 ExecutablePath: /usr/bin/update-manager GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'593' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'484' b'com.ubuntu.update-manager' b'launch-time' b'1478762256' InstallationDate: Installed on 2015-03-24 (596 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to yakkety on 2016-11-02 (7 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "software-updater-bug.png" https://bugs.launchpad.net/bugs/1640717/+attachment/4775213/+files/software-updater-bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640717 Title: Software Updater input events go to the wrong control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1640717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1382661] Re: Support for JLINK in 0.8.0 requires small patch
The fix is most definitely in the SF repo: http://sourceforge.net/p/openocd/code/ci/96549bf0121a7cff08885ddca22ab7a1c362ea24/ You may want to check that you're using the correct URL, SF changed it a few years back and unfortunately the old one is still available but frozen. The correct one is: http://git.code.sf.net/p/openocd/code By the way, the patch only helps in the odd case where libusb-1.0 is unavailable so libusb-0.1 is used instead. This is not a recommended configuration, since adapter drivers that only work with libusb-1.0 API will not be built. I recommend to install libusb-1.0-0-dev before the configure step, then the patch won't be needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1382661 Title: Support for JLINK in 0.8.0 requires small patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openocd/+bug/1382661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986983] Re: Opening Empthay from the Indicator also opens the Preference window
Why was this marked invalid? It's an obvious bug which can be reproduced like in comment #8. In short, after running empathy -p once, the preference windows opens every time the empathy windows is raised by executing empathy, even without the -p. Interestingly, even when starting using the option -h, --start-hidden Don't display the contact list or any other dialogs on startup the preferences dialog still pops up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986983 Title: Opening Empthay from the Indicator also opens the Preference window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/986983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 429510] Re: package dahdi 1:2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Just a thought... Is DAHDI really required for asterisk? I was about to install asterisk in a linux container, but since it depends on dahdi it had to pull in all sorts of linux kernel packages which are nonsensical and probably would fail inside a container. If it's not required, maybe dahdi should be be moved from depends to recommends in asterisk? That would likely solve the reporter's problem. -- package dahdi 1:2.2.0-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/429510 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 397750] Re: mouse : input : event field not found
I'm having the same problem here, with current karmic. My logs have gotten cluttered like this for ages, but it's not until now I realised what's causing these messages. I have a Logitech MX500 mouse, with buttons above and below the scroll wheel to scroll up/down just by holding one of these buttons. Every time I push it, every time I release it, and a load of times when I move the mouse while pressing it, one of these lines gets logged. Seriously annoying, especially when scrolling in the System Log Viewer :P -- mouse : input : event field not found https://bugs.launchpad.net/bugs/397750 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 354136] Re: unintuitive back and forward
** Bug watch added: GNOME Bug Tracker #578837 http://bugzilla.gnome.org/show_bug.cgi?id=578837 ** Also affects: fileroller via http://bugzilla.gnome.org/show_bug.cgi?id=578837 Importance: Unknown Status: Unknown -- unintuitive back and forward https://bugs.launchpad.net/bugs/354136 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 354136] [NEW] unintuitive back and forward
Public bug reported: Binary package hint: file-roller The back and forward buttons don't work the way they do in other applications (web browsers, nautilus,...). Consider an archive with the following directory structure: / /a /a/b /a/c After browsing from / to /a to /a/b, you press Back and get to /a. Browse to /a/c and press Back to /a. One would expect that pressing Back again would get you to the directory from which you first got to /a, which is /. Instead you end up in /a/b. The attached patch corrects the behavior to match nautilus, which deletes all forward history when you browse to a new location. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/file-roller Package: file-roller 2.24.1-0ubuntu2 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 SourcePackage: file-roller Uname: Linux 2.6.27-11-generic i686 ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- unintuitive back and forward https://bugs.launchpad.net/bugs/354136 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 354136] Re: unintuitive back and forward
** Attachment added: file-roller-2.24.1_history-fix.diff http://launchpadlibrarian.net/24711317/file-roller-2.24.1_history-fix.diff ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24711318/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/24711319/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/24711320/ProcStatus.txt -- unintuitive back and forward https://bugs.launchpad.net/bugs/354136 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 354136] Re: unintuitive back and forward
Oops, maybe should free the element data as well. ** Attachment added: file-roller-2.24.1_history-fix2.diff http://launchpadlibrarian.net/24728371/file-roller-2.24.1_history-fix2.diff -- unintuitive back and forward https://bugs.launchpad.net/bugs/354136 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 61361] Re: Machine won't boot because fstype misidentifies ext3 filesystem as minix
I still have this problem in Dapper with klibc-utils 1.1.16-1ubuntu5 -- Machine won't boot because fstype misidentifies ext3 filesystem as minix https://launchpad.net/bugs/61361 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
