[Bug 2063234] [NEW] rsibreak reports once per second kf5idletime_wayland: This plugin does not support polling idle time
Public bug reported: rsibreak is generating this message which ends up in the journal *very second* kf5idletime_wayland: This plugin does not support polling idle time $ journalctl | grep rsibreak | head Mar 22 06:21:21 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:22 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:23 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:24 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:25 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:26 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:27 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:28 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:29 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time Mar 22 06:21:30 clamps rsibreak[5422]: kf5idletime_wayland: This plugin does not support polling idle time $ journalctl `type -p rsibreak` | grep "This plugin" | wc -l 858265 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: rsibreak 4:0.12.15-1build2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Apr 23 11:07:11 2024 InstallationDate: Installed on 2020-02-15 (1529 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: rsibreak UpgradeStatus: Upgraded to noble on 2024-04-11 (12 days ago) ** Affects: rsibreak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063234 Title: rsibreak reports once per second kf5idletime_wayland: This plugin does not support polling idle time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsibreak/+bug/2063234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor
A victim of some other fix. This regression can be prevented by adding amdgpu.dc=0 to the kernel command line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762818 Title: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor
** Attachment added: "Xorg log when booting with 18.04 kernel" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762818 Title: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762818] [NEW] Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor
Public bug reported: Symptom: booting 18.04 kernel reduces resolution available while 17.10 kernel (on 18.04) does not I have a 3 identical monitor setup - all at 2560x1600 native resolution. If I boot the current 18.04 kernel 4.15.0-13-generic then the third monitor does not have the native resolution available. If I reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors have the native resolution available. On the video card the monitors are connected to HDMI, DisplayPort and DVI. On the monitors themselves the connectors are HDMI, DisplayPort and HDMI. (3rd monitor is using DVI to HDMI cable.) Xorg logs show identical EDID information between the kernels. 18.04's just decides to not make 2560x1600 available, having 2048x1080 or 1920x1200 as the highest. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 10 12:17:31 2018 DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev e5) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 450/455/460/560] [1458:230a] LightdmGreeterLogOld: ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug 7 2015, 01:24:18) ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: indicator-application main process (1456) killed by TERM signal MachineType: Supermicro C7Z170-SQ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@ SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago) dmi.bios.date: 12/19/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: C7Z170-SQ dmi.board.vendor: Supermicro dmi.board.version: 1.01A dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: C7Z170-SQ dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic resolution ubuntu ** Attachment added: "Xorg log when booting with 17.10 kernel" https://bugs.launchpad.net/bugs/1762818/+attachment/5109700/+files/oldkernel.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762818 Title: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1510570] Re: BLE pairing fail
Based on comments here I can get the Microsoft Arc Touch Bluetooth to pair. But the Bluetooth manager doesn't think it is a mouse, or offer connecting it to the input service. How does one get an actual working mouse? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1510570 Title: BLE pairing fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1254970] Re: clang failed to link binaries when -flto option is used.
And clang 3.8 in Ubuntu 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1254970 Title: clang failed to link binaries when -flto option is used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-snapshot/+bug/1254970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
The mailing list eventually went nowhere, including someone helping me out privately. He seemed to think it was a udev issue, which was highly amusing as the udev (and systemd) binaries were running from the very devices they believed weren't ready yet. Here is the final scorecard. I have 3 systems, all using btrfs with raid0 across two devices. Both root and home are separate subvolumes on that. System 1 (workstation - above report): systemd brings the system up but times out waiting to mount home. Setting /home to nofail in fstab and then running mount -a from a console works just fine. This is the only system where the two drives are identical - they are exactly the same SSD models and firmware versions on the same controller. (Note system fails to boot if they are on different controllers which wasn't a problem with earlier Ubuntu versions.) Booting with upstart works fine and is how I have now configured the system. System 2 (laptop): the two devices are wrapped in LUKS+dmcrypt. They are decrypted at boot and then there is a pause, and then finally everything comes up. Most of the time that pause is 3 minutes, but sometimes is a few seconds. Again no problems in earlier Ubuntu releases. System 3 (server): Like system 1, it is bare devices but in this case they are about the same capacity but from different vendors. Everything works perfectly, and if anything boots a bit faster than earlier Ubuntu releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1453952] Re: Wildcards in ALLOWDEVFILE Not Working
Some of them go away when you include wildcards. I have this in rkhunter.conf: ALLOWDEVFILE=/dev/shm/byobu-*/*/* That suppresses most of the warnings, with some remaining due to being hidden files or directories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1453952 Title: Wildcards in ALLOWDEVFILE Not Working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/1453952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462046] [NEW] Incorrect btrfs ready invocation 64-btrfs.rules
Public bug reported: /lib/udev/rules.d/64-btrfs.rules This invokes btrfs ready $devnode. However that will always give a usage error. The correct invocation is as follows (note added device). btrfs device ready $devnode ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: udev 219-7ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: XFCE CustomUdevRuleFiles: 51-android.rules 60_smfpautoconf_samsung.rules 61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 60-vboxdrv.rules Date: Thu Jun 4 10:39:36 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/lib/systemd/systemd udev.log-priority=debug rd.udev.log-priority=debug SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-04-23 (41 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462046 Title: Incorrect btrfs ready invocation 64-btrfs.rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1462046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1462046] Re: Incorrect btrfs ready invocation 64-btrfs.rules
Supposedly 'btrfs ready $devnode' is internal to udev and unrelated to the similarly named btrfs device ready command ** Changed in: systemd (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1462046 Title: Incorrect btrfs ready invocation 64-btrfs.rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1462046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
I will ask on the mailing list. It is failing to mount /home. The lines in /etc/fstab for root and /home are identical, except that one is subvol=@ and one is subvol=@home. Root mounts just fine. When it comes time to mount /home, systemd is trying to check the filesystem but that isn't going succeed as all the parts are already mounted for root. There are some logs included in earlier responses. No clues as to the actual problem though. I will reboot and get the logs for your request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
** Attachment added: systemctl status fsck services https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405782/+files/systemd-fsck-star-service-status.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
** Attachment added: systemctl output https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405785/+files/systemctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
Outputs from the root shell you get dumped to on an unsuccessful boot. I did reboot back into it at one point because it kept saying that logs had been rotated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
** Attachment added: systemctl status of * (everything) https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405784/+files/status-all.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
** Attachment added: /proc/mounts https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405783/+files/procmounts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs consisting of multiple partitions fails
Message thread in mailing list at http://thread.gmane.org/gmane.comp.sysutils.systemd.devel/32245 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs consisting of multiple partitions fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails with non-unique UUIDs
@pitti: please can you change the title to something that isn't so misleading. That would let others realise this same bug affects them. With btrfs if you make a filesystem consist of multiple partitions then each of those partitions will get the same UUID because they are all parts of the same filesystem. This is not incorrect behaviour. PARTUUID and UUID_SUB will be unique per partition as expected, but those are not what you use in /etc/fstab I did a fresh install in Virtualbox with a RAID 0 btrfs and @ and @home subvolumes and it did work. My real system with considerably more drives is more complicated. How do I troubleshoot this? I need to know what systemd thinks it is doing and why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails with non-unique UUIDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448834] Re: mouse battery not shown after upgrade
I didn't know how much of this stuff had been folded in systemd, or is affected by udev/hotplug etc :-) In any event, I just retested and plugging the mouse into a 14.10 machine has upower show the mouse, and plugging into two different 15.04 systems will not show it (one upstart, one systemd). Can this be moved to upower or do I need to submit a new bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448834] Re: mouse battery not shown after upgrade
The power manager plugin is greyed out so I can't add it - http://i.imgur.com/X5K3loz.png $ upower -d Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Fri 24 Apr 2015 02:38:01 PM PDT (1019180 seconds ago) has history: no has statistics: no unknown warning-level: none icon-name: '' Daemon: daemon-version: 0.99.2 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep (This is a desktop system so it doesn't have batteries, lids etc.) Also note that I am running upstart and not systemd, because systemd outsmarts itself trying to mount filesystems. Martin Pitt changed the bug title to something incorrect which I can't fix - https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails with non-unique UUIDs
Apologies for misleading you - I thought you were more familiar with btrfs. The summary change is incorrect and btrfs is doing the right thing. Quite simply the filesystem is made up of more than one partition, so more than one partition correctly has the same UUID. But that also means looking at /dev/disk/by-uuid/UUID can only point to one of the partitions making up the filesystem UUID. The btrfs wiki talks about multiple devices: https://btrfs.wiki.kernel.org/index.php/Using_Btrfs_with_Multiple_Devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails with non-unique UUIDs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448834] [NEW] mouse battery not shown after upgrade
Public bug reported: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) ** Affects: xfce4-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1448834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
$ sudo btrfs fi show Label: 'main' uuid: 3ff68715-0daa-4e44-8de2-0997f36d8ab6 Total devices 2 FS bytes used 408.16GiB devid2 size 894.25GiB used 319.03GiB path /dev/sdb1 devid3 size 894.25GiB used 319.03GiB path /dev/sda1 Label: 'newspace' uuid: 9c0be64e-1841-445a-ac85-b2b46e92e5d8 Total devices 1 FS bytes used 2.00TiB devid1 size 3.58TiB used 2.33TiB path /dev/sdc2 Label: 'backups' uuid: b02cc605-dd78-40bc-98a5-8f5543d83b66 Total devices 1 FS bytes used 662.07GiB devid1 size 1.58TiB used 667.06GiB path /dev/sdd2 Label: none uuid: a877962c-c242-4517-8f5a-ae8da82bab64 Total devices 2 FS bytes used 113.36GiB devid1 size 207.74GiB used 65.03GiB path /dev/sdf3 devid2 size 208.67GiB used 65.03GiB path /dev/sde2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
I also got the status for dev-disk-by\x2duuid- 3ff68715\x2d0daa\x2d4e44\x2d8de2\x2d0997f36d8ab6.device/start which just had messages about file/directory not found without saying which ones it was looking for. (To be clear the status for that job was found just fine - the contents of the status is what complained. I lost the file due to rebooting etc.) The uuid it is stuck on there is the one of the filesystem containing subvols @ and @home, and is shared by both parts - /dev/sda1 and /dev/sdb1. Also note that reverse lookups such as /dev/disk/by- uuid/3ff68715-0daa-4e44-8de2-0997f36d8ab6 can only point to one those two (sdb1 right now). And just to make life more interesting the SSDs are one set of two identical 256GB and one set of two identical 960GB. ** Attachment added: blkid.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383539/+files/blkid.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
The weird device= lines were me trying to work around a different regression. I have two hard drive controllers on the motherboard - a 4 port one from Intel and a 4 port one from ASMedia. I also have 6 devices plugged in (8 at one point). Before 15.04 I placed the drives randomly, and it turned out that one half of root was on the Intel controller and the other half was on the ASMedia controller. That worked fine before 15.04. With 15.04 the btrfs device scan step was run after the first controller was detected, but before/during the second one.That meant that root couldn't be mounted by initramfs because the second half hadn't been found by the earlier btrfs device scan. In theory adding the device= bits would make that work. In practise they didn't. Since I needed a working system I had to change cables so that both devices were on the same first detected controller at which point mounting root worked. I've attached lshw output from right now (ie after moving devices). ** Attachment added: lshw.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383427/+files/lshw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
** Attachment added: fsckd-status.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383527/+files/fsckd-status.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
** Attachment added: fsck-root-status.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383526/+files/fsck-root-status.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] Re: fscking btrfs mount fails
The problem is actually the mounting of /home not root. As you can see from the fstab they are identical except for the subvol= parameter. Note that I also tried removing the device= bits, updating the initramfs and trying again. It made no difference. ** Attachment added: journal.txt https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4383524/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: fscking btrfs mount fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447879] [NEW] Systemd outsmarts itself with btrfs
Public bug reported: I have two SSDs in raid0 (striped) configuration with my root and home as separate subvolumes. This setup has worked fine for several Ubuntu releases, but fails with systemd on 15.04. systemd does manage to mount root, but then looks like it is trying to fsck the disk for home which is nonsensical. After 90 seconds it drops into a useless shell where I can't fix things. Relevant lines from /etc/fstab UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 / btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@ 0 1 UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home btrfs defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home 0 2 Note how the lines are identical except for the subvol value. I originally didn't have the device= bits either but had to add it for root because of how `btrfs device scan` is run. With or without it present doesn't make any difference for home. There is no such problem booting with upstart ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 23 19:45:38 2015 MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf nomdmonisw init=/sbin/upstart SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 1 overridden configuration files found. UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447879 Title: Systemd outsmarts itself with btrfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912431] Re: Preseeded 12.04 grub-install failed: Wrong number of args: mapdevfs path
Just did a fresh text install (twice) of 14.04 and the install grub step failed with exactly the same symptoms. Trying to do things manually results in a boot where I get dumped into initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912431 Title: Preseeded 12.04 grub-install failed: Wrong number of args: mapdevfs path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer-utils/+bug/912431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 490917] Re: initrd on Karmic does not support multiple encrypted LVM physical volumes.
This bug is still present and another scenario is btrfs. cryptroot is written under the assumption there is exactly one device that needs to be decrypted for root to be mounted, which can be very wrong for btrfs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/490917 Title: initrd on Karmic does not support multiple encrypted LVM physical volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/490917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
Another Ubuntu release and this is still broken. As a reminder if you use the keyscript then you will *not* be able to enter passwords, either in graphical mode (plymouth) or text mode (recovery). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289977] Re: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found
I just got bitten by this doing a fresh install of 14.04 with two drives. For whatever reason it decided to write to a different device than it had previously resulting in an unbootable system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289977 Title: Ubuntu 14.04 Update breaks grub, resulting in error: symbol 'grub_term_highlight_color' not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1289977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
All I know is that whatever the cause was, it was fixed in 3.12 even in the rcs. I have no idea what the actual fix was. Kernel 3.11 end of lifed November last year. I also use btrfs for which there have been maintenance patches in 3.12. I followed the Kernel Build and Installation section at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
You do know that no one knows what the fix is, only that it is in 3.12? You can see that Timo gave up trying to find it in mid-November. If Ubuntu is actually going to figure out the fix and backport it, then go for it. However I am extremely sceptical and had to devise my own workaround. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
Kernel 3.12 even in the prereleases fixed this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
It isn't invalid. This is a very real issue affecting the existing Ubuntu release. I have been personally compiling 3.12 kernels from kernel.org as a workaround that works for me, so I don't need anything. I'd suggest closing as Won't Fix since Ubuntu won't provide a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
If Ubuntu would actually backport the 3.12 kernel to Saucy then go for it. The kernel team PPA does not do 3.12 for saucy. At a minimum 3.12.6 is needed due to lots of btrfs fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
Can you point me to other builds you want me to try, ideally as ppa links like the above? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
I'm confused as to what the goal is. The drm-intel-nightly works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
This didn't work: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.7-saucy/ This did: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/ It would be ideal if you gave me a list of urls like above in preferred testing order -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
I installed 3.12 from http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.12-saucy/ It failed to boot. With normal boot there was no further progress after ramdisk loading. In recovery mode the kernel said it failed to execute /init but gave no further details. I am now trying http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel- nightly/2013-11-07-saucy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
The drm-nightly from previous comment works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
Booting the raring kernel (3.8.0-33) under saucy results in all 3 monitors working correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215449] Re: triple monitor support not working on HD 4600
Which driver did you get working in the end? My experience was having 3 monitors work fine in raring 13.04, until the driver that is in Saucy 13.10 at which point it started pulling the only two monitors at a time stunt. Bug 1242180 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215449 Title: triple monitor support not working on HD 4600 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1215449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
xrandr output running command line from comment 2. Raring: crtc 0:1920x1200 60.0 +1920+0 DP2 crtc 1:1920x1080 60.0 +3840+0 HDMI1 crtc 2:1920x1080 60.0 +0+0 HDMI3 Saucy livecd: xrandr: Configure crtc 2 failed crtc 0:1920x1080 60.0 +3840+0 HDMI1 crtc 1:1920x1080 60.0 +0+0 HDMI3 crtc 2:1920x1200 60.0 +1920+0 DP2 crtc 0: disable crtc 1: disable crtc 2: disable crtc 3: disable screen 0: revert crtc 0: revert crtc 1: revert crtc 2: revert crtc 3: revert -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
@RichardNeill - already did all that as mentioned in comment 4 which also has the advantage of working on the livecd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
** Attachment added: xorg log https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884152/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
The failures to set occur using the graphical tool from system settings, as well as the xrandr command line xrandr --output DP2 --primary --auto --output HDMI3 --auto --left-of DP2 --output HDMI1 --auto --right-of DP2 ** Attachment added: xrandr output https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884151/+files/xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] [NEW] saucy regression - three monitors no longer work
Public bug reported: I've just upgraded from raring. There I had 3 monitors attached to my Intel HD Graphics 4000 (i7 3770 cpu) where it all works perfectly. (Two monitors are identical flanking my centre displayport monitor.) In saucy I can get any two monitors working, and any attempt to get all 3 working results in an error about setting crtc with a different number. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Sat Oct 19 14:28:59 2013 MarkForUpload: True SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to saucy on 2013-10-19 (0 days ago) ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
I also ran xorg-edgers-live-test as described in https://wiki.ubuntu.com/XorgOnTheEdge and that didn't help. Restored from my backup and everything works fine. (xorg-edgers-live-test also needs updating - it tries to restart gdm when it should be restarting lightdm) ** Attachment added: xrandr output from raring where everything works fine https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884308/+files/xrandr.raring.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242180] Re: saucy regression - three monitors no longer work
** Attachment added: xorg log from raring where everything works fine https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+attachment/3884309/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242180 Title: saucy regression - three monitors no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1242180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212008] Re: Perl fix needed
I have no idea on the other Ubuntu versions as I only use 13.04. I did use awstats on the past, but had been using Google Analytics for over a year. In the comments linked from the report there is another user reporting only coming across the problem on upgrade to 13.04. I didn't provide a patch. It is the diff between awstats 7.1 and 7.1.1 showing what the changes were in addition to fixing this specific issue. ie it is information to help decide between adding a single caret or just updating to 7.1.1. It doesn't matter to me what you do. My setup is working because I edited awstats.pl and added the caret. I don't have a test reproduction for you because the issue is regarded as a bug and experienced by others. That is why there are links in the description and the awstats team made a 7.1.1 release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+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 1212008] Re: Perl fix needed
I have no idea on the other Ubuntu versions as I only use 13.04. I did use awstats on the past, but had been using Google Analytics for over a year. In the comments linked from the report there is another user reporting only coming across the problem on upgrade to 13.04. I didn't provide a patch. It is the diff between awstats 7.1 and 7.1.1 showing what the changes were in addition to fixing this specific issue. ie it is information to help decide between adding a single caret or just updating to 7.1.1. It doesn't matter to me what you do. My setup is working because I edited awstats.pl and added the caret. I don't have a test reproduction for you because the issue is regarded as a bug and experienced by others. That is why there are links in the description and the awstats team made a 7.1.1 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212008] Re: Perl fix needed
What happens is that awstats ignores over 99% of your log entries. Note that this is done silently - ie there are no log messages or error codes. It is only after human inspection that you notice it doesn't look right. Even after you get it working again it skips old entries and I don't know how to make it reconsider the ones from the period of ignoring. So it makes awstats dangerous and the output useless. In my case it also deleted the logs because I have PurgeLogFile=1 You should either fix this or remove the package - it is that bad. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+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 1212008] Re: Perl fix needed
The only thing needed to fix the bug is the caret in the regular expression. I've attached the diff between 7.1. and 7.1.1 which includes that change, and adds detection of Windows 8. I'd be happy with either change (just the caret or bump to 7.1.1) ** Patch added: Diff between awstats 7.1 and 7.1.1 https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+attachment/3772352/+files/awstats-7.1-to-7.1.1.diff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+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 1212008] Re: Perl fix needed
What happens is that awstats ignores over 99% of your log entries. Note that this is done silently - ie there are no log messages or error codes. It is only after human inspection that you notice it doesn't look right. Even after you get it working again it skips old entries and I don't know how to make it reconsider the ones from the period of ignoring. So it makes awstats dangerous and the output useless. In my case it also deleted the logs because I have PurgeLogFile=1 You should either fix this or remove the package - it is that bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212008] Re: Perl fix needed
The only thing needed to fix the bug is the caret in the regular expression. I've attached the diff between 7.1. and 7.1.1 which includes that change, and adds detection of Windows 8. I'd be happy with either change (just the caret or bump to 7.1.1) ** Patch added: Diff between awstats 7.1 and 7.1.1 https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+attachment/3772352/+files/awstats-7.1-to-7.1.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1212008] [NEW] Perl fix needed
Public bug reported: The currently shipping awstats is incompatible with perl 5.14. A fix was applied (correctly) in awstats 7.1.1. http://www.howtoforge.com/forums/showthread.php?p=297288#post297288 http://sourceforge.net/p/awstats/discussion/43430/thread/474fdb3e/ I manually applied the change (adding a caret in the expression) and now am getting all the expected data rather than having the majority missing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: awstats 7.1~dfsg-1 [modified: usr/share/awstats/tools/update.sh] ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Aug 13 15:20:25 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: awstats UpgradeStatus: Upgraded to raring on 2013-05-19 (86 days ago) ** Affects: awstats (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+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 1212008] [NEW] Perl fix needed
Public bug reported: The currently shipping awstats is incompatible with perl 5.14. A fix was applied (correctly) in awstats 7.1.1. http://www.howtoforge.com/forums/showthread.php?p=297288#post297288 http://sourceforge.net/p/awstats/discussion/43430/thread/474fdb3e/ I manually applied the change (adding a caret in the expression) and now am getting all the expected data rather than having the majority missing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: awstats 7.1~dfsg-1 [modified: usr/share/awstats/tools/update.sh] ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Tue Aug 13 15:20:25 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: awstats UpgradeStatus: Upgraded to raring on 2013-05-19 (86 days ago) ** Affects: awstats (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1212008 Title: Perl fix needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1212008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 657338] Re: Special function keys and lid events don't work after first suspend/resume
** Changed in: linux (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/657338 Title: Special function keys and lid events don't work after first suspend/resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/657338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390959] Re: 045e:00b0 Microsoft keyboard and 045e:0745 nano transceiver recognised as joystick - interferes with some games
This bug is still present in 13.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390959 Title: 045e:00b0 Microsoft keyboard and 045e:0745 nano transceiver recognised as joystick - interferes with some games To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/390959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1184736] [NEW] Failed to lookup path for root 0
Public bug reported: btrfs subvolume list is giving error message Failed to lookup path for root 0 This has been fixed in btrfs tools but not the version shipping with Raring. http://forums.funtoo.org/viewtopic.php?id=2028 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: btrfs-tools 0.19+20130117-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon May 27 12:57:51 2013 MarkForUpload: True SourcePackage: btrfs-tools UpgradeStatus: Upgraded to raring on 2013-04-28 (29 days ago) ** Affects: btrfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1184736 Title: Failed to lookup path for root 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs-tools/+bug/1184736/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181674] [NEW] told to upgrade to version I'm already at
Public bug reported: After an upgrade from 12.10 to 13.04 on two different machines using do- release-upgrade (ie command line upgrade), they both say this on login: Welcome to Ubuntu 13.04 (GNU/Linux 3.8.0-21-generic x86_64) * Documentation: https://help.ubuntu.com/ New release '13.04' available. Run 'do-release-upgrade' to upgrade to it. Note how I am being told to run do-release-upgrade to the version it is already at. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubuntu-release-upgrader-core 1:0.192.10 ProcVersionSignature: Ubuntu 3.8.0-21.32-generic 3.8.8 Uname: Linux 3.8.0-21-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CrashDB: ubuntu Date: Sun May 19 00:11:54 2013 MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to raring on 2013-05-19 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181674 Title: told to upgrade to version I'm already at To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1181674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179834] [NEW] baobab hangs at startup
Public bug reported:
When I run baobab nothing happens - I don't get a window or when started
from a console any messages, even after waiting for several minutes.
strace has this at the end with the hanging:
geteuid() = 1000
getegid() = 1000
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, revents=POLLOUT}])
sendmsg(11, {msg_name(0)=NULL, msg_iov(1)=[{\0, 1}], msg_controllen=32,
{cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=13565,
uid=1000, gid=1000}}, msg_flags=0}, MSG_NOSIGNAL) = 1
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, revents=POLLOUT}])
sendto(11, AUTH\r\n, 6, MSG_NOSIGNAL, NULL, 0) = 6
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, REJECTED EXTERNAL DBUS_COOKIE_SH..., 4096, 0, NULL, NULL) = 36
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, revents=POLLOUT}])
sendto(11, AUTH EXTERNAL 31303030\r\n, 24, MSG_NOSIGNAL, NULL, 0) = 24
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, OK 41b3c3c0a40c65fd7d45c7c85191f..., 4096, 0, NULL, NULL) = 37
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, revents=POLLOUT}])
sendto(11, NEGOTIATE_UNIX_FD\r\n, 19, MSG_NOSIGNAL, NULL, 0) = 19
poll([{fd=11, events=POLLIN}], 1, 4294967295) = 1 ([{fd=11, revents=POLLIN}])
recvfrom(11, AGREE_UNIX_FD\r\n, 4096, 0, NULL, NULL) = 15
poll([{fd=11, events=POLLOUT}], 1, 4294967295) = 1 ([{fd=11, revents=POLLOUT}])
sendto(11, BEGIN\r\n, 7, MSG_NOSIGNAL, NULL, 0) = 7
write(8, \1\0\0\0\0\0\0\0, 8) = 8
futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 13
write(13, \1\0\0\0\0\0\0\0, 8)= 8
poll([{fd=13, events=POLLIN}], 1, 0)= 1 ([{fd=13, revents=POLLIN}])
write(13, \1\0\0\0\0\0\0\0, 8)= 8
close(13) = 0
eventfd2(0, O_NONBLOCK|O_CLOEXEC) = 13
write(13, \1\0\0\0\0\0\0\0, 8)= 8
write(8, \1\0\0\0\0\0\0\0, 8) = 8
futex(0x14a0250, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x1618400, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x16183d0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 4294967295) = 1 ([{fd=13, revents=POLLIN}])
read(13, \1\0\0\0\0\0\0\0, 16)= 8
poll([{fd=13, events=POLLIN}], 1, 4294967295^C unfinished ...
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: baobab 3.6.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
Date: Tue May 14 01:27:58 2013
MarkForUpload: True
SourcePackage: baobab
UpgradeStatus: Upgraded to raring on 2013-04-28 (16 days ago)
** Affects: baobab (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1179834
Title:
baobab hangs at startup
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/baobab/+bug/1179834/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1179396] [NEW] limit to loopback interface doesn't work for ipv6/5800
Public bug reported: In dconf I have the network-interface configured to lo (loopback). I use ssh with port forwarding so I don't need or want vino externally accessible. While port 5900 ends up restricted to localhost, port 5800 is not: $ netstat -an | grep -i tcp | grep -i listen tcp0 0 127.0.0.1:5900 0.0.0.0:* LISTEN tcp0 0 127.0.1.1:530.0.0.0:* LISTEN tcp0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:17500 0.0.0.0:* LISTEN tcp0 0 0.0.0.0:17501 0.0.0.0:* LISTEN tcp6 0 0 :::5800 :::*LISTEN tcp6 0 0 ::1:5900:::*LISTEN tcp6 0 0 :::5298 :::*LISTEN tcp6 0 0 :::22 :::*LISTEN tcp6 0 0 ::1:631 :::*LISTEN $ lsof -i tcp:5800 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME vino-serv 10382 rogerb 16u IPv6 50199 0t0 TCP *:5800 (LISTEN) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: vino 3.6.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Mon May 13 00:08:23 2013 MarkForUpload: True SourcePackage: vino UpgradeStatus: Upgraded to raring on 2013-04-28 (15 days ago) ** Affects: vino (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1179396 Title: limit to loopback interface doesn't work for ipv6/5800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1179396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1037325] Re: xhci_hcd event logging every 3 seconds
I still get this in Ubuntu 13.04 with ubuntu kernel 3.8.0-19-generic but not every 3 seconds - The period varies from 20 seconds to 1,000 seconds seemingly random. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1037325 Title: xhci_hcd event logging every 3 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1037325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
Another Ubuntu release and this is still broken. To reiterate - in theory using decrypt_keyctl as shipped by Ubuntu solves the problem. In practise it results in an unbootable machine because the mechanisms used to ask for the password do not work. #7 provides the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065302] Re: _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them
** Summary changed: - _FORTIFY_SOURCE being added for ppa builds + _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065302 Title: _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apsw/+bug/1065302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065302] Re: _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them
Building for raring ppa is also broken for the same reason. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065302 Title: _FORTIFY_SOURCE being added syntactically wrong for ppa builds breaking them To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apsw/+bug/1065302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065302] Re: _FORTIFY_SOURCE being added for ppa builds
I am talking about my PPA builds, *not* the Ubuntu supplied package which is always dreadfully out of date. When I use pbuilder locally everything builds fine. The same dsc when running on Ubuntu's PPA build mechanism is adding D_FORTIFY_SOURCE=2 the wrong way. dh_pycentral is used because the same package is built in ppas for multiple Ubuntu versions going back to 10.04. dh_pycentral does work for every version other than Quantal PPA build (but local is fine). If there is a different helper that is compatible then I'll use it, but you need to tell me which one it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065302 Title: _FORTIFY_SOURCE being added for ppa builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apsw/+bug/1065302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065302] Re: _FORTIFY_SOURCE being added for ppa builds
@Scott: the problem is not the addition of the flags. I have no problem
with them being added, being different for PPAs or anything like that.
The problem is that the flags are added in an *invalid way*. See a more
detailed recent/build log at https://launchpadlibrarian.net/128659634
/buildlog_ubuntu-quantal-amd64.python-
apsw_3.7.15.2-r1-1ppa1~quantal1_FAILEDTOBUILD.txt.gz
ie the flags are supposed to be added like this: [ ('_FORTIFY_SOURCE', '2'),
('FOO', 'BAR') ] which translates into
#define _FORTIFY_SOURCE 2
#define FOO BAR
Instead this is being supplied: [ '_FORTIFY_SOURCE', '2' ] which translates
into
#define _FORTIFY_SOURCE
#define 2
The PPA system is messing up the *syntax* of how it adds the flags, and
then that causes the builds to fail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065302
Title:
_FORTIFY_SOURCE being added for ppa builds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apsw/+bug/1065302/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992724] Re: can't open .vnc file anymore after upgrading ubuntu from 11.10 to 12.04
Even after capitalization and using the config above I still get the error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992724 Title: can't open .vnc file anymore after upgrading ubuntu from 11.10 to 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/992724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898986] Re: Printing does not work on Samsung CLP-610ND
@Johann, thank you for that pointer. I had tried the official Samsung driver earlier which has the world's worst installer and on printed to half the page width. Using the latest driver from bchemnet I found the following: * Using the Samsung Configurator meant no print jobs came out and I was constantly told about non-existent paper jams * Using system-config-printer with DNS-SD/LPD printed and also claimed paper jams via notification popups * Using system-config-printer with Jetdirect printed and there were no popups but the printer icon and successfully completed job icons all have explanation marks saying there were paper jams * I did some test prints including the multi-coloured text which doesn't come out with Samsung's PCL and was murky with Samsung's Windows SPL-C driver That leads to the following conclusions: * Samsung's printers do not do PCL emulation correctly * There are several open source SPL-C drivers but none of them work correctly * Samsung's current binary SPL-C driver does generate correct output * Samsung's engineers should be ashamed at the packaging and components of their driver * The bchemnet repackaging undoes most of the Samsung packaging and security issues * Use as little Samsung code as possible (eg only use the Configurator to access scanner functionality - not present in my printer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898986 Title: Printing does not work on Samsung CLP-610ND To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/898986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091561] [NEW] Breaks on directories with spaces in their names
Public bug reported: One of my projects has a directory with spaces in its name. When any of the files in the directory are changed the window just shows the first word from the directory name with a weird icon and none of the affected files. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gitg 0.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Tue Dec 18 00:29:52 2012 MarkForUpload: True SourcePackage: gitg UpgradeStatus: Upgraded to quantal on 2012-10-12 (67 days ago) ** Affects: gitg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091561 Title: Breaks on directories with spaces in their names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1091561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091561] Re: Breaks on directories with spaces in their names
This may be related to #591670 which deals with files having spaces in their names (my case is the containing directory). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091561 Title: Breaks on directories with spaces in their names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gitg/+bug/1091561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
When I examined the code it actually only stores the password in the system keyring for 60 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067563] [NEW] Exits on any download error (regression)
Public bug reported: I have several repositories including some vendor ones (eg virtualbox) and many ppa's. If update-manager has any problem downloading any of those non-Ubuntu provided repositories then it exits at the end. I then have to run it a second time, abort the repository downloads and then I can install outstanding updates. A common reason for repositories failing to download is ppa's not providing packages for the current Ubuntu release. They eventually will, so I'm happy to leave the ppas enabled until they do provide them. There is no particular reason for update-manager to unilaterally decide to exit on repository download failure. And if it is going to then at least only do it if the download failures were for the official Ubuntu repositories. This is a regression - versions prior to quantal would tell you of the errors, and then let you install updated packages. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Tue Oct 16 17:10:58 2012 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1350432526' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'922' b'com.ubuntu.update-manager' b'window-width' b'964' PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to quantal on 2012-10-12 (4 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067563 Title: Exits on any download error (regression) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1067563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066057] [NEW] suspend doesn't work
Public bug reported: After upgrading to quantal suspend from the menu no longer works (pm- suspend works just fine). .xsession-errors contains this relevant line: gnome-session[2937]: libupower-glib-CRITICAL: up_client_get_can_suspend: assertion `UP_IS_CLIENT (client)' failed ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-session 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Fri Oct 12 10:34:05 2012 PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: Upgraded to quantal on 2012-10-12 (0 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066057 Title: suspend doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1066057/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065806] [NEW] diff window is too small on upgrade
Public bug reported: When running update-manager -d to upgrade from precise to quantal on two different machines I would be prompted to view the diffs between two files. However the window that appears is not resizeable and it only shows two lines which is completely unusable. See attached screenshot for an example ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: update-manager 1:0.174.3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu3 Aptdaemon: Architecture: amd64 Date: Thu Oct 11 20:33:51 2012 GsettingsChanges: b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'launch-time' b'1349900623' b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'922' b'com.ubuntu.update-manager' b'window-width' b'964' PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: Upgraded to quantal on 2012-10-12 (0 days ago) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal ** Attachment added: Screenshot from 2012-10-11 19:40:47.png https://bugs.launchpad.net/bugs/1065806/+attachment/3395805/+files/Screenshot%20from%202012-10-11%2019%3A40%3A47.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065806 Title: diff window is too small on upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1065806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065302] [NEW] _FORTIFY_SOURCE being added for ppa builds
Public bug reported: I'm the author of apsw - https://code.google.com/p/apsw/ - and have a PPA for builds for various Ubuntu versions at https://launchpad.net /~ubuntu-rogerbinns/+archive/apsw/+packages This has worked fine for a few years. However builds for Quantal are failing. You can see a failed build log at https://launchpadlibrarian.net/119421086/buildlog_ubuntu-quantal-amd64 .python-apsw_3.7.14.1-r1-1ppa1~quantal1_FAILEDTOBUILD.txt.gz - The way I do the ppa build is by running make ppa from a source tree. The cause is because _FORTIFY_SOURCE is being mishandled. Its definition and usage is not coming from my code. I can't tell if the problem is the server side environment having a bug or something involved in making packages for submission is adding it. Perhaps the Python stuff on 12.04 (where I do the ppa submissions) is putting in gunk that breaks 12.10? Attached is a .build file from the client machine. It contains the following line which is not my doing dpkg-buildpackage: export CPPFLAGS from dpkg-buildflags (origin: vendor): -D_FORTIFY_SOURCE=2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: python-dev 2.7.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Wed Oct 10 15:39:41 2012 SourcePackage: python-defaults UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise ** Attachment added: python-apsw_3.7.14.1-r1-1ppa1~quantal1_source.build https://bugs.launchpad.net/bugs/1065302/+attachment/3393972/+files/python-apsw_3.7.14.1-r1-1ppa1%7Equantal1_source.build -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065302 Title: _FORTIFY_SOURCE being added for ppa builds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1065302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
** Changed in: cryptsetup (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
I'm trying that, and especially need to verify it will work from initramfs as my root is encrypted. Ironically it stores the passphrase in the kernel forever, whereas something that temporarily stores the passphrase while the initramfs is running would have it available for considerably less time! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
It turns out that the script is already in the right place and all the initramfs hooks are in place etc. It is merely necessary to add keyscript=decrypt_keyctl into the relevant places in crypttab. Unfortunately doing so causes update-initramfs to fail with the cryptkeyctl hook giving error code 1. Still investigating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
Ok, more progress. keyctl must be installed otherwise update-initramfs fails and you have to guess why. And with everything plumbed in, I can't actually enter my passphrase and the machine is unusable. The reason is decrypt_keyctl is not using whatever means is correct for prompting for the passphrase. Before I would get the prompt on the main Ubuntu screen (logo and 5 animated dots). That screen just animates forever. If I switch consoles I do end up on one that says Caching passphrase for : as what looks like a prompt, but I can't get it to accept anything. In recovery mode the animated ubuntu screen is not present, instead just a text mode. I get a prompt this time, but again can't get it to accept anything. If I switch to the dmesg console, nothing is echoed until I hit return. At that point decrypt_keyctl just says No key available for this passphrase against the UUID of each encrypted device and then I am dumped out at the (initramfs) shell. So yeah, using it as things stand is a solution in spirit but in practise leaves you with an unbootable machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
I got everything working. The README you pointed to is very misleading since the script is already in the correct place. I'd be inclined to just delete the README, and mention all the different scripts in /lib/cryptsetup/scripts in the main crypttab page. decrypt_keyctl doesn't seem like 'none' as the third column in crypttab (either that or the ordering confuses it). I changed the ordering so swap was last, and the third column from 'none' to avoid multiple prompts. In cryptdisk.functions there is a section that tries to work out what program to use for prompting (look for plymouth). In decrypt_keyctl there is a similar section at the top trying to do the same thing, but it doesn't look for plymouth. I made two changes: 1) Added code to make plymouth be probed and used. At the top section as the last entry: test -x /bin/plymouth plymouth --ping PW_READER_='plymouth' In the case $PW_READER_ section: plymouth) KEY_=$(plymouth ask-for-password --prompt $PROMPT_) || die Error executing plymouth ;; That makes things work perfectly when plymouth is present. 2) In recovery mode things were unusable. That was because it was using askpass. I commented out the line beginning test -x $ASKPASS_ which means that in a non-plymouth environment the stty mode is being used. The stty mode worked just fine in recovery mode. In any event as things currently are shipped on Ubuntu you will have an unbootable system if you follow the README instructions. Either decrypt_keyctl should be removed, or fixed. The documentation should at least mention the script, and also mention that keyutils must be installed. It should also mention having to run update-initramfs on changing /etc/crypttab askpass is broken. It should really be fixed to be able to do plymouth if it is running, or the various things (eg stty method that the decrypt_keyctl is doing). Then everything can just use askpass. Failing that the logic for picking a password prompt program should be unified into one place. For example it could be put into a function in cryptdisk.functions and that sourced/used by decrypt_keyctl. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026432] [NEW] Uninformative display with multiple batteries
*** This bug is a duplicate of bug 880881 *** https://bugs.launchpad.net/bugs/880881 Public bug reported: My laptop has two batteries (Lenovo Thinkpad) with the main one and a second one instead of the DVD drive. This indicator correctly knows that there are two batteries - clicking on it to get the menu shows both batteries and their (separate) statuses. However the icon/text display only shows the first battery. This system drains the second battery completely first. The text display will just say 100% until the second is drained at which point it starts counting down. Similarly it only shows charge remaining time for the first battery. (The drop down does show correct information.) The calculations should be summed over all batteries in the system. For example the time remaining depends on the sum of all battery remaining charges divided by the sum of all battery discharge rates and something similar being applicable for charge time. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-power 2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jul 18 20:40:56 2012 SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026432 Title: Uninformative display with multiple batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1026432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1026432] Re: Uninformative display with multiple batteries
*** This bug is a duplicate of bug 880881 *** https://bugs.launchpad.net/bugs/880881 ** This bug has been marked a duplicate of bug 880881 Power indicator does not combine multiple battery status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1026432 Title: Uninformative display with multiple batteries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1026432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] [NEW] initramfs should try password against other devices
Public bug reported: Due to multiple drives I have multiple encrypted volumes. The passphrase for all of them is identical.. However at boot I am asked the password for each one, and have to type the same thing over and over again. cryptsetup during boot should at least try the previously typed in password against each volume. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cryptsetup (not installed) ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jul 9 22:14:32 2012 SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022815] Re: initramfs should try password against other devices
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022815 Title: initramfs should try password against other devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022651] [NEW] crytptab man page should mention running update-initramfs
Public bug reported: http://manpages.ubuntu.com/manpages/precise/en/man5/crypttab.5.html That man page should mention running `update-initramfs -c -k all'. The reason is that some of the content of crypttab is copied into the initramfs. Consequently you can end up changing the file itself over and over and it has no effect until the initramfs is next rebuilt. As far as I can tell the content that is copied is the root file system and swap. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cryptsetup (not installed) ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jul 9 10:26:06 2012 SourcePackage: cryptsetup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022651 Title: crytptab man page should mention running update-initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022651] Re: crytptab man page should mention running update-initramfs
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022651 Title: crytptab man page should mention running update-initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1022651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965371] Re: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04
Another server this fails for is Google Appengine. If Ubuntu aren't going to fix openssl then please at least change Python standard libraries to work around it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965371 Title: HTTPS requests fail on sites which immediately close the connection if TLS 1.1 negotiation is attempted, on Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/965371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 898986] Re: Printing does not work on Samsung CLP-610ND
I just tried again with a fresh install of Precise with my 620ND. By default the foomatic driver is picked and it defaults to monochrome. I tried printing this bug page as my test. I don't know if the blame is with Chrome or the driver, but it behaves as though the top and bottom margins are 0 but I did get the output. system-config-printer shows a red exclamation mark and claims a media jam even though there isn't one. If I switch to colour mode then the printer machinery whirs a lot, the display says Ready and nothing comes out. I went to change the driver. Only foo2qpdl is listed for this model and the ones around it. printer-driver-splix is installed and its package description claims ... and color (CLP-5xx, CLP-6xx) models are supported. I went to the 660ND selection in the printer driver selector and picked the pxlcolor option. The page took an extraordinary amount of time to print (many minutes) from Chrome. eog was relatively instant but bizarrely it printed on the back of the paper so the printer printed a blank page, sucked it back in through the duplexer and then printed it. Libreoffice didn't have the delay issues either. In the generic driver section there is also Gutenprint offered for PCL 6, but that did not support colour. The firmware bugs that result in botched large single colour text being the wrong colour or coming out white are still exposed when using PCL 6, but not present when using PCL 5c. The final conclusion is that to use this printer you need to choose PCL 5c or PCL 6. PCL 5c: Prints large coloured text fine, but takes a long time to print images (and possibly lower quality too) PCL 6: Messes up large coloured text, prints images quickly Also you will always have an icon indicating there is a paper jam even though there isn't. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/898986 Title: Printing does not work on Samsung CLP-610ND To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/898986/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016818] Re: Immediate crash on startup
I submitted the crash numerous times to Mozilla. It didn't give me any feedback other than saying I could relaunch. In any event I did use apport to report the bug here and the doc you posted says Note that the Apport hook provided from Firefox and Thunderbird 13 will automatically attach the ID's of crash reports you submitted to Mozilla, so you don't need to look for these manually as long as you submit the bug report using Apport! That would appear not to work, nor do I have any idea if the mozilla submission opened anything, and if it did what the ids are. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016818 Title: Immediate crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016818] Re: Immediate crash on startup
Crash ID: bp-ce7dfec4-b140-4b3d-8cbc-ca5a72120623 Crash ID: bp-1ecdd5bf-c42f-49eb-9c54-0dfc82120622 Crash ID: bp-ec5f55d4-db94-4fa4-a17c-ce3d82120622 Crash ID: bp-012114a9-6ba4-41f1-a532-8a5042120622 Crash ID: bp-257ae38f-21d5-4eea-88e9-9c2862120622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016818 Title: Immediate crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016818] [NEW] Immediate crash on startup
Public bug reported: Thunderbird received a version bump today. After Update Manager installed the new version, any attempts to launch Thunderbird result in an immediate crash. This happens even if I remove ~/.thunderbird ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 13.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rogerb 2467 F pulseaudio /dev/snd/controlC0: rogerb 2467 F pulseaudio /dev/snd/pcmC0D0p: rogerb 2467 F...m pulseaudio BuildID: 20120615181619 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf312 irq 49' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,80860033,0014' Controls : 51 Simple ctrls : 24 Card1.Amixer.info: Card hw:1 'CinemaTM'/'Microsoft Microsoft® LifeCam Cinema(TM) at usb-:00:1d.0-1.7.2, high speed' Mixer name : 'USB Mixer' Components : 'USB045e:075d' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 56 Mono: Capture 47 [84%] [27.00dB] [on] Channel: release Date: Fri Jun 22 23:06:35 2012 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.53 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Locales: extensions.sqlite corrupt or missing PrefSources: /etc/thunderbird/syspref.js prefs.js user.js Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615181619 RfKill: RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to precise on 2012-04-30 (54 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5936.2011.0630.2250 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5936.2011.0630.2250:bd06/30/2011:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: ftp_proxy: http://192.168.1.25:8080 http_proxy: http://192.168.1.25:8080 ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise release-channel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016818 Title: Immediate crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016818] Re: Immediate crash on startup
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016818 Title: Immediate crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1016818] Re: Immediate crash on startup
Attached is an strace of startup with a deleted ~/.thunderbird ** Attachment added: Strace of startup (strace -f -o tb.strace thunderbird) https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+attachment/3201279/+files/tb.strace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1016818 Title: Immediate crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1016818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 973096] Re: Nvidia driver causes xorg crash
I'm another user affected by this with an 8800GT that has been rock solid stable in prior Ubuntu releases. I'm running the gnome shell fallback mode. The current, current-updates and x-swat repository versions all resulted in random crashes back to the login screen. I've tried using the noveau driver instead but it increasingly loses its marbles over time. After about 8 hours of uptime it starts flickering random bits of random windows in random places on the screen, and gets progressively worse. It also hangs the X server inputs for a few seconds while doing this. Consequently neither binary nor noveau driver provide a usable desktop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/973096 Title: Nvidia driver causes xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/973096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
