[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)
how to get these files from Ubuntu 15.04 (Vivid) - whithout installing it ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1369113 Title: Steam game began crashing 2014-09-12 (cross-post Source bugtracker) Status in steam package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am cross-posting this issue, which I reported to Valve's Source GIT issue tracker, because it was suggested that the regression may be due to Ubuntu Xorg changes rather than changes on the Steam end. Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822 Symptom -- DoD:Source loads normally. But after a few minutes of playing (not a specific time as far as I can tell), the game freezes in place. A short clip (maybe a quarter of a second) of the last audio that played then repeats over and over on a loop. The process has to be killed manually with a QUIT or HUP signal for good measure. This is a new issue that just arose today. I have included system info, kernel log, and output when game is run from terminal and crashes. X info -- X.Org X Server 1.16.0 Release Date: 2014-07-16 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug Build Date: 10 September 2014 01:10:01PM xorg-server 2:1.16.0-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.32.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. System -- OS: Ubuntu 14.10 (latest updates) Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64 Model: HP Envy x360 lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4) 00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI Express Card Reader (rev 01) 08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b) 09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) Kernel log excerpt (from game start through crash end) -- Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open] Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW context 1 destroyed Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open] Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW context 1 created Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] [CONNECTOR:14:?] Sep 12 19:11:25 kernel: [ 4447.852796] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] [CONNECTOR:14:eDP-1] Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD on Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 0x8008 PP_CONTROL: 0xabcd000f Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 00e04c Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA Extension found Sep 12 19:11:25 kernel: [ 4447.853711] [drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] probed modes : Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline]
[Touch-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
would somebody kill this stupid logevent soon ? deletec the folder, purged/reinstalled logrotate, few minutes later 16GB log filling up disk again. This waste laptop runtime - how to disable this freaking mess ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in mediascanner package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389021] Re: Does not detect hotplugged storage device (exfat)
please tell how tp properly install this upgraded package on 14.10. (I doubt adding repositories for vivid is a good idea) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1389021 Title: Does not detect hotplugged storage device (exfat) Status in util-linux package in Ubuntu: Fix Released Bug description: It used to work then stopped for some reason. Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x7c367968 Device Boot Start End Sectors Size Id Type /dev/sdb1 63 488392064 488392002 232.9G 7 HPFS/NTFS/exFAT exfatfsck /dev/sdb1 finds no error mount -t exfat works, it's just auto-mounting that doesn't. '-t' is required though, not sure if that's normal: mount: /dev/sdb1: more filesystems detected. This should not happen, use -t type to explicitly specify the filesystem type or use wipefs(8) to clean up the device. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gvfs 1.20.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 4 00:39:03 2014 HotplugNewDevices: /dev/sdb1 /dev/sdb HotplugNewMounts: InstallationDate: Installed on 2014-10-03 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gvfs Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1389021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393206] Re: SD/mmc card with exFAT fs not automatically mounted since upgrade to utopic
I have the same problem with a normal session.
a manual mount like :
sudo mount -t exfat /dev/sdb1 /media/exfat /media/manual
works fine.
this goes for all Gopro3 64GB cards (exFAT formatted)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1393206
Title:
SD/mmc card with exFAT fs not automatically mounted since upgrade to
utopic
Status in lightdm package in Ubuntu:
Incomplete
Bug description:
Inserting a memory card formatted with exFAT in my built-in memory
reader doesn't automatically mount the partition since I upgraded to
utopic (from trusty). Before this it mounted the partition without any
problems. I have installed exfat-fuse and exfat-utils as before.
udisks2 detects the partition correctly but gvfs ignores it:
17:00:48.133: Added /org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95
org.freedesktop.UDisks2.Drive:
CanPowerOff:false
Configuration: {}
ConnectionBus: sdio
Ejectable: false
Id: SU64G-0xa21a0d95
Media: flash_sd
MediaAvailable: true
MediaChangeDetected:true
MediaCompatibility: flash_sd
MediaRemovable: true
Model: SU64G
Optical:false
OpticalBlank: false
OpticalNumAudioTracks: 0
OpticalNumDataTracks: 0
OpticalNumSessions: 0
OpticalNumTracks: 0
Removable: true
Revision:
RotationRate: 0
Seat: seat0
Serial: 0xa21a0d95
SiblingId:
Size: 63864569856
SortKey:01hotplug/1416153648130773
TimeDetected: 1416153648130773
TimeMediaDetected: 1416153648130773
Vendor:
WWN:
17:00:48.134: Added /org/freedesktop/UDisks2/block_devices/mmcblk0
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0
DeviceNumber: 45824
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0
ReadOnly: false
Size: 63864569856
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95
org.freedesktop.UDisks2.PartitionTable:
Type: dos
17:00:48.183: Added /org/freedesktop/UDisks2/block_devices/mmcblk0p1
org.freedesktop.UDisks2.Block:
Configuration: []
CryptoBackingDevice:'/'
Device: /dev/mmcblk0p1
DeviceNumber: 45825
Drive:
'/org/freedesktop/UDisks2/drives/SU64G_0xa21a0d95'
HintAuto: true
HintIconName:
HintIgnore: false
HintName:
HintPartitionable: true
HintSymbolicIconName:
HintSystem: false
Id:
IdLabel:
IdType:
IdUUID:
IdUsage:
IdVersion:
MDRaid: '/'
MDRaidMember: '/'
PreferredDevice:/dev/mmcblk0p1
ReadOnly: false
Size: 63863521280
Symlinks: /dev/disk/by-id/mmc-SU64G_0xa21a0d95-part1
org.freedesktop.UDisks2.Partition:
Flags: 0
IsContained:false
IsContainer:false
Name:
Number: 1
Offset: 1048576
Size: 63863521280
Table: '/org/freedesktop/UDisks2/block_devices/mmcblk0'
Type:
UUID:
Drive connected:'SU64G'
Drive(0): SU64G
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
