[Touch-packages] [Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."
File descriptor 84 (/dev/pts/7) leaked on lvs invocation. Parent PID 13547: /bin/sh File descriptor 84 (/dev/pts/7) leaked on lvs invocation. Parent PID 11219: /usr/sbin/grub-probe File descriptor 84 (/dev/pts/7) leaked on vgs invocation. Parent PID 14875: /usr/sbin/grub-probe I have this on a Ubuntu 14.10 system( multiboot with fedora 20 and windows 7) when executing "apt-get autoremove" the old kernel was not removed, but it was removed after running "apt-get autoremove" a second time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/591823 Title: "File descriptor \d+ (\S+) leaked on lvs invocation." Status in aptitude: Confirmed Status in lvm2 - Logical Volume Manager: Fix Released Status in “lvm2” package in Ubuntu: Opinion Bug description: If you see messages like these: File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent PID 1854: /bin/sh You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings. Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138 This is a slightly controversial bug and it's not yet fixed either way (aka fix not to leak file descriptors or stop warning by default) To manage notifications about this bug go to: https://bugs.launchpad.net/aptitude/+bug/591823/+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 1382510] Re: systemd-logind upstart script breaks if libpam-systemd is installed for more than one arch
This bug was fixed in the package systemd - 204-5ubuntu20.8
---
systemd (204-5ubuntu20.8) trusty; urgency=medium
[ Ben Howard ]
* 75-persistent-net-generator.rules: Add new Microsoft net rule
(LP: #1367883)
[ Martin Pitt ]
* debian/libpam-systemd.systemd-logind.upstart: Fix "PAM module installed"
check for the case when there is more than one library installed, which
can happen on multi-arch systems. Thanks Grzegorz Gutowski! (LP: #1382510)
-- Martin PittWed, 29 Oct 2014 08:05:16 +0100
** Changed in: systemd (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1382510
Title:
systemd-logind upstart script breaks if libpam-systemd is installed
for more than one arch
Status in “systemd” package in Ubuntu:
Fix Released
Status in “systemd” source package in Trusty:
Fix Released
Bug description:
/etc/init/systemd-logind.conf contains the following:
# only start if PAM module is actually available, not if libpam-systemd is
# removed but not purged
[ -e /lib/*/security/pam_systemd.so ] || { stop; exit 0; }
Which is a wrongly written script. It assumes that there is at most one file
matching the wildcard. It is not true in my system.
If your system have both libpam-systemd:amd64 and libpam-systemd:i386 then:
# ls /lib/*/security/pam_systemd.so
/lib/i386-linux-gnu/security/pam_systemd.so
/lib/x86_64-linux-gnu/security/pam_systemd.so
and you get the following:
# cat /var/log/upstart/systemd-logind.log
/proc/self/fd/9: 4: [: /lib/i386-linux-gnu/security/pam_systemd.so:
unexpected operator
systemd-logind stop/pre-start, process 2462
systemd-logind does not start at all. This causes many bad things to
happen later.
There are many ways to fix this. For my purposes I removed the faulty
line from the file. I don't know what is the expected behaviour. Maybe
this one:
ls /lib/*/security/pam_systemd.so &> /dev/null || { stop; exit 0; }
This bug might be the root cause of other bugs. Like this one:
#1372187 (and #1377727)
SRU TEST CASE
=
- On an amd64 system, run "sudo apt-get install libpam-systemd:i386"
- Then run "sudo restart systemd-logind"
- On current trusty this will result in stop/waiting, with the error in
/var/log/upstart/systemd-logind.log as above.
- With this fix this will result in start/running and no error.
My system info:
# lsb_release -rd
Description: Ubuntu 14.04.1 LTS
Release: 14.04
# apt-cache policy libpam-systemd
libpam-systemd:
Installed: 204-5ubuntu20.7
Candidate: 204-5ubuntu20.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1382510/+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 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
This bug was fixed in the package systemd - 204-5ubuntu20.8 --- systemd (204-5ubuntu20.8) trusty; urgency=medium [ Ben Howard ] * 75-persistent-net-generator.rules: Add new Microsoft net rule (LP: #1367883) [ Martin Pitt ] * debian/libpam-systemd.systemd-logind.upstart: Fix "PAM module installed" check for the case when there is more than one library installed, which can happen on multi-arch systems. Thanks Grzegorz Gutowski! (LP: #1382510) -- Martin PittWed, 29 Oct 2014 08:05:16 +0100 ** Changed in: systemd (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: In Progress Status in “systemd” source package in Trusty: Fix Released Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+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 1364466] Re: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner-service-2.0': double free or corruption (fasttop): ADDR ***
I have tested with the results of #1386571 , and the problem still remains. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1364466 Title: /usr/bin/mediascanner-service-2.0:*** Error in `mediascanner- service-2.0': double free or corruption (fasttop): ADDR *** Status in “gstreamer” package in Ubuntu: Confirmed Status in “mediascanner2” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mediascanner2. This problem was most recently seen with version 0.104+14.10.20140825-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/354f10fdaba609ee33dd0a2868637ec79c590b56 and https://errors.ubuntu.com/problem/01fcf2789e27c0abf6922c68c02a408b907fab83 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer/+bug/1364466/+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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
modem interface... Is there anyway to edit comments? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: In Progress Status in The Savilerow project: New Status in “network-manager” package in Ubuntu: Incomplete Status in “ofono” package in Ubuntu: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+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 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
According to dbus-monitor, the mode interface keeps failing:
signal sender=:1.8 -> dest=(null destination) serial=1635
path=/org/freedesktop/NetworkManager/Devices/1;
interface=org.freedesktop.NetworkManager.Device; member=StateChanged
uint32 120
uint32 40
uint32 0
signal sender=:1.8 -> dest=(null destination) serial=1636
path=/org/freedesktop/NetworkManager/Devices/1;
interface=org.freedesktop.NetworkManager.Device.Modem; member=PropertiesChanged
array [
dict entry(
string "State"
variant uint32 120
)
dict entry(
string "StateReason"
variant struct {
uint32 120
uint32 0
}
)
]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1357321
Title:
[TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
Status in Platform API:
In Progress
Status in The Savilerow project:
New
Status in “network-manager” package in Ubuntu:
Incomplete
Status in “ofono” package in Ubuntu:
New
Status in “qtbase-opensource-src” package in Ubuntu:
In Progress
Bug description:
scope images load fine in wifi, but not on hsdpa even when there is
good connectivity and browsing works well. Results are return, but
images do not load.
To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1357321/+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
Re: [Touch-packages] [Bug 1390994] Re: Lost ability to print duplex
As I stated in my report, my HP 8600 Printer has a duplexer unit. Requests for double-sided printing (from Ubuntu) worked properly until a recent Ubuntu upgrade. The duplexer works properly in local manual mode, just as it did before. The problem I'm reporting is that it appears that something in Ubuntu has changed that now causes the double-sided option to be disregarded. Print jobs run normally, but disregard requests for two-sided printing; pages print sindge-sided only. The print interface menu display has been changed (and not necessarily for the better). The GUI display shows double-sided printing to be enabled with long-edge option, as its predecessor did before, but double-sided printing never occurs, though I have requested numerous such jobs. At the time I write this, there are only two lines in the cups error log, each one stating: Unknown directive BrowseAddress on line 26 of /etc/cups/cups.conf less reports that there is no such file as /etc/cups/cups.conf (and, yes, I used sudo) Wilbur Killebrew On 11/10/2014 01:07 PM, Pascal De Vuyst wrote: > Does your printer have a duplex unit or are you using some kind of > manual duplex mode (print the odd pages, then the paper gets put back > into the input tray and the even pages get printed)? > > Can your follow the instructions of the sections "CUPS error_log", > "Capturing print job data", and "Getting the data which would go to the > printer" on https://wiki.ubuntu.com/DebuggingPrintingProblems. Can you > also attach the file(s) which you tried to print? Please do this for all > situations with problems (LibreOffice, evince, ...). > > Do not pack the obtained file together and do not compress them. Please > attach them one by one. This will make it easier for the readers > of this > bug report to handle them. > > ** Changed in: cups (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1390994 Title: Lost ability to print duplex Status in “cups” package in Ubuntu: Incomplete Bug description: A recent update (about a week or two ago) has resulted in my HP 8600 printer no longer printing double-sided. All the configuration information appears to be unchanged, but pages are not printed double- sided, when requested. The duplexer works properly in local mode. My configuration is: Ubuntu 14.04 (up-to-date), HP Pavilion dv6 with AMD quad-core processor. I have been running Ubuntu on this machine for about 27 months. I successfully upgraded from 12.04 to 14.04 last summer. The 8600 printer has been in use for about two years. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1390994/+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 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot
[Expired for unity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: unity (Ubuntu) Status: Incomplete => Expired -- 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/1357681 Title: System tray icons for Owncloud, Insync and Dropbox disapear after reboot Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: I have used 3 clients for file synchronization: Owncloud Client, Dropbox and Insync. Apparently the bug applies to all of the applications. Within the last 2-3 months the icons for the the applications have started to disappear from the system tray after a reboot. The icons doesn't reappear when (re)launching the applications from dash or terminal. However if I run "killall owncloud; owncloud" the icon for owncloud (re)appears. The icons for Dropbox and Insync also (re)appears when using "killall" before launching. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 16 11:33:31 2014 DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-01-15 (212 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 09:12:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1357681/+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 1357681] Re: System tray icons for Owncloud, Insync and Dropbox disapear after reboot
[Expired for Unity because there has been no activity for 60 days.] ** Changed in: unity Status: Incomplete => Expired -- 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/1357681 Title: System tray icons for Owncloud, Insync and Dropbox disapear after reboot Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: I have used 3 clients for file synchronization: Owncloud Client, Dropbox and Insync. Apparently the bug applies to all of the applications. Within the last 2-3 months the icons for the the applications have started to disappear from the system tray after a reboot. The icons doesn't reappear when (re)launching the applications from dash or terminal. However if I run "killall owncloud; owncloud" the icon for owncloud (re)appears. The icons for Dropbox and Insync also (re)appears when using "killall" before launching. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Aug 16 11:33:31 2014 DistUpgraded: 2014-02-21 20:58:31,099 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-01-15 (212 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=0a466d6e-f0bc-4c34-bcc1-9649cb723803 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-21 (175 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.2-0intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.2-0intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911-0intel1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 09:12:00 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1357681/+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 1384286] Re: add directory allowing scopes and apps to share data
** Changed in: unity-scopes-api (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “click-reviewers-tools” package in Ubuntu:
In Progress
Status in “unity-scopes-api” package in Ubuntu:
Fix Committed
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/rw,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+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 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Won't Fix ** Changed in: hwe-next/trusty Assignee: Hui Wang (hui.wang) => (unassigned) ** Changed in: hwe-next/trusty Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work Status in HWE Next Project: Fix Released Status in HWE Next trusty series: Triaged Status in HWE Next utopic series: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Won't Fix Status in “systemd” source package in Trusty: In Progress Bug description: CID: 201402-14663 Dell Latitude 12 Rugged Extreme The microphone mute key does not work on this system, so as its LED Steps: 1. Install 14.04 + update (3.13.0-30), boot to desktop 2. Try to mute the microphone with the hotkey (fn+F4) Expected results: * Mic mute key should work, its LED should be lit and the "Mute" option for input device should be ticked after you press the mic mute key. Actual result: * Nothing happened. Debugging information: ubuntu@201402-14663:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 29 press ^Ccaught signal 2, cleaning up... xev cannot detect any microphone mute key event ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1501 F pulseaudio /dev/snd/controlC0: ubuntu 1501 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jul 9 23:57:11 2014 HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734 InstallationDate: Installed on 2014-07-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0TH1GJ dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 12 Rugged Extreme (7204) dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+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 1384286] Re: add directory allowing scopes and apps to share data
Sorry for being so dense. I had the wrong mental model because, all
along, I assumed that the cache_directory was to be used for sharing, so
I was thinking that the proposal was to change the location of the
existing cache dir, instead of adding a completely new one.
The linked branch should fix this.
** Branch linked: lp:~michihenning/unity-scopes-api/app-directory
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu
in Ubuntu.
https://bugs.launchpad.net/bugs/1384286
Title:
add directory allowing scopes and apps to share data
Status in “apparmor-easyprof-ubuntu” package in Ubuntu:
In Progress
Status in “click-reviewers-tools” package in Ubuntu:
In Progress
Status in “unity-scopes-api” package in Ubuntu:
In Progress
Bug description:
Summary says it all, just need to decide on the directory. I propose using
this rule:
# Allow scopes to share data with the app shipped in the same click
owner @{HOME}/.local/share/@{APP_PKGNAME}/rw,
owner @{HOME}/.local/share/@{APP_PKGNAME}/** mrwkl,
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1384286/+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 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
guycarre is right in that this is a gnome/unity problem most likely. I can confirm Ubuntu server 14.04.1 does not have this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in “openssh” package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+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 1339998] Re: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work
The kernel change for Trusty is to control the mute led status, It is difficult to backport the dell mute led controlling patch to trusty kernel since the driver framework has greatly changed. But fortunately we have alsa daily dkms, this fix was already in the alsa daily dkms for Trusty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1339998 Title: [Dell Latitude 12 Rugged Extreme 7204] Microphone mute key does not work Status in HWE Next Project: Fix Released Status in HWE Next trusty series: New Status in HWE Next utopic series: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “systemd” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Incomplete Status in “systemd” source package in Trusty: In Progress Bug description: CID: 201402-14663 Dell Latitude 12 Rugged Extreme The microphone mute key does not work on this system, so as its LED Steps: 1. Install 14.04 + update (3.13.0-30), boot to desktop 2. Try to mute the microphone with the hotkey (fn+F4) Expected results: * Mic mute key should work, its LED should be lit and the "Mute" option for input device should be ticked after you press the mic mute key. Actual result: * Nothing happened. Debugging information: ubuntu@201402-14663:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 248 press keycode 248 release keycode 29 press ^Ccaught signal 2, cleaning up... xev cannot detect any microphone mute key event ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-30-generic 3.13.0-30.55 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1501 F pulseaudio /dev/snd/controlC0: ubuntu 1501 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jul 9 23:57:11 2014 HibernationDevice: RESUME=UUID=b68f02ad-f5e4-4eb9-b88d-e85f60666734 InstallationDate: Installed on 2014-07-10 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Latitude 12 Rugged Extreme (7204) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed root=UUID=bdd00fe9-0df9-4b71-92c5-5f94c533f725 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-30-generic N/A linux-backports-modules-3.13.0-30-generic N/A linux-firmware 1.127.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 0TH1GJ dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd05/12/2014:svnDellInc.:pnLatitude12RuggedExtreme(7204):pvr01:rvnDellInc.:rn0TH1GJ:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 12 Rugged Extreme (7204) dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1339998/+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 1367883] Re: [SRU] Add Microsoft-owned MAC address to 75-persistent-net-generator.rules
Tagging based on comment #10. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in “systemd” package in Ubuntu: Fix Released Status in “udev” package in Ubuntu: Invalid Status in “udev” source package in Precise: In Progress Status in “systemd” source package in Trusty: Fix Committed Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+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 1389008] Re: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control)
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound- override-v2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1389008 Title: Often fails to connect to Pulseaudio and unity-notifications (results in missing volume notifications and improper volume control) Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-touch-session” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Confirmed Status in “indicator-sound” package in Ubuntu RTM: Invalid Status in “ubuntu-touch-session” package in Ubuntu RTM: Confirmed Status in “unity8” package in Ubuntu RTM: New Bug description: Often after boot indicator-sound fails to connect to Pulseaudio and to unity-notifications using libnotify. Therefore, volume notifications aren't shown and changes to the volume role go unnoticed, which then results in improper volume control. As already mentioned in the original bug description, running "restart indicator-sound" resolves the issue. Original description: Happens often after phone boot where changing volume by touch or by phone buttons. Volume correctly changes, but the org.freedesktop.Notifications popup isn't displayed. The problem seems fixes itself if you run "restart indicator-sound", so maybe there's an issue with i-sound and unity-notifications starting at the same time, with the former querying the latter's capabilities before it's ready for business? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1389008/+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 978604] Re: Banshee/Rhythmbox regularly stop playing audio when left on in the background
I can confirm this bug under Ubuntu 14.10 64-bit (Unity), Rhythumbox 3.0.3 . Syslog shows just the one relevant entry that matches up with the time of occurrence. Nov 13 11:11:58 aubnerap06183l pulseaudio[2434]: [alsa-sink-92HD81B1X5 Analog] protocol-native.c: Failed to push data into queue Pattern is always the same. Rhythmbox minimised playing a longish playlist. Get a few tracks in, and it will play a fraction of a second of a new track then halt. Clicking play/pause won't re-start playback, but moving the slider back to the beginning of the track will. Often I will go for a while without it happening, but once it does it seems to then occur again on nearly every new track. I've experienced the same under Ubuntu 14.04, and before that on 12.04 going back as far as my initial Ubuntu install in mid 2012. Behavior hasn't altered at all over the last 2 years. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/978604 Title: Banshee/Rhythmbox regularly stop playing audio when left on in the background Status in “pulseaudio” package in Ubuntu: Confirmed Status in “pulseaudio” source package in Precise: Confirmed Bug description: If Banshee or Rhythmbox is left playing in the background they will randomly stop playing in the latest builds of Ubuntu 12.04. Starting a new piece of music usually fixes the problem. If left to its own devices, the music will start playing again at some random time, at some random position. This problem exists on both my desktop machine (custom built Intel machine) and my laptop (Macbook 5,1). It has been happening for several months now. I became frustrated enough to load up pulseaudio in debugging mode. The log shows that when the music player just finishes playing one piece, and tries to start the next piece, you see something like this: --- ( 335.399| 34.388) D: [alsa-sink] sink-input.c: Requesting rewind due to corking ( 335.400| 0.001) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: before: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: after: 3705 ( 335.400| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 14820 bytes. ( 335.400| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.400| 0.000) D: [alsa-sink] sink.c: latency = 1643 ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on render memblockq. ( 335.400| 0.000) D: [alsa-sink] sink-input.c: Have to rewind 14820 bytes on implementor. ( 335.400| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.400| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.001) D: [alsa-sink] alsa-sink.c: hwbuf_unused=0 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: setting avail_min=15502 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c:in dB: 0: -28.11 dB 1: -28.11 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Got hardware volume: 0: 34% 1: 34% ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -28.00 dB 1: -28.00 dB ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Calculated software volume: 0: 100% 1: 100% (accurate-enough=yes) ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: in dB: 0: -0.11 dB 1: -0.11 dB ( 335.402| 0.000) D: [alsa-sink] sink.c: Volume not changing ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Requested to rewind 65536 bytes. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Limited to 15300 bytes. ( 335.402| 0.000) D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1b.0.analog-stereo becomes idle, timeout in 5 seconds. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: before: 3825 ( 335.402| 0.000) D: [pulseaudio] core.c: Hmm, no streams around, trying to vacuum. ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: after: 3825 ( 335.402| 0.000) D: [alsa-sink] alsa-sink.c: Rewound 15300 bytes. ( 335.402| 0.000) D: [alsa-sink] sink.c: Processing rewind... ( 335.402| 0.000) D: [alsa-sink] sink.c: latency = 1402 ( 335.402| 0.000) D: [alsa-sink] source.c: Processing rewind... ( 335.402| 0.000) I: [pulseaudio] sink-input.c: Freeing input 3 "'zero-project - 05 - Forest of the unicorns' by 'zero-project'" ( 335.402| 0.000) D: [pulseaudio] module-stream-restore.c: Not restoring device for stream sink-input-by-media-role:music, because already set to 'alsa_output.pci-_00_1b.0.analog-stereo'. ( 335.403| 0.000) D: [pulseaudio] module-intended-roles.c: Not setting device for stream Playback Stream, because alrea
[Touch-packages] [Bug 1391243] Re: [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
Confirmed on utopic. But vivid does not have the bug (file is installed
correctly).
** Summary changed:
- libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
+ [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
** Summary changed:
- [utopic] libg1-mesa-dev doesn't create /usr/lib/i386-linux-gnu/libGL.so link
+ [utopic] libg1-mesa-dev doesn't create any libGL.so link
** Changed in: mesa (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1391243
Title:
[utopic] libg1-mesa-dev doesn't create any libGL.so link
Status in “mesa” package in Ubuntu:
New
Bug description:
Package version installed: 10.3.0-0ubuntu3
Ubuntu release: Utopic (normal upgrade from Trusty)
Trying to build OpenGL-depending program I run ./configure script
which tries to invoke «glBegin» with gcc and -lGL, and it fails.
I have both libgl1-mesa-{dev,dri,glx} and fglrx-updates{,-dev} installed, and
only manual symlinking helps.
Alhough I wanted fglrx libGL.so.1.2 symlinked, none is being symlinked, so
it's bad in its current state.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libgl1-mesa-dev 10.3.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
BootLog: * Starting Deluge BitTorrent Daemon deluged
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Nov 10 19:40:31 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
fglrx-updates-core, 14.201, 3.16.0-23-generic, i686: installed
fglrx-updates-core, 14.201, 3.16.0-25-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
(prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fa34]
Subsystem: Toshiba America Info Systems Device [1179:fa34]
InstallationDate: Installed on 2013-10-30 (376 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
LightdmGreeterLog: ** (lightdm-gtk-greeter:6257): WARNING **: Failed to load
user image: Failed to open file '/home/reslayer/.face': No such file or
directory
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:5685): WARNING **: Failed to
load user image: Failed to open file '/home/reslayer/.face': No such file or
directory
MachineType: TOSHIBA Satellite C50D-A-K8K
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PT10AN
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvr1.10:bd05/22/2013:svnTOSHIBA:pnSatelliteC50D-A-K8K:pvrPSCH2R-00700JRU:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C50D-A-K8K
dmi.product.version: PSCH2R-00700JRU
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 28 04:22:34 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1
xserver.video_driver: fglrx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1391243/+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 1391243] Re: [utopic] libg1-mesa-dev doesn't create any libGL.so link
Sorry, not confirmed yet. I was only testing trusty and vivid. Neither
of them have the bug at least.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1391243
Title:
[utopic] libg1-mesa-dev doesn't create any libGL.so link
Status in “mesa” package in Ubuntu:
New
Bug description:
Package version installed: 10.3.0-0ubuntu3
Ubuntu release: Utopic (normal upgrade from Trusty)
Trying to build OpenGL-depending program I run ./configure script
which tries to invoke «glBegin» with gcc and -lGL, and it fails.
I have both libgl1-mesa-{dev,dri,glx} and fglrx-updates{,-dev} installed, and
only manual symlinking helps.
Alhough I wanted fglrx libGL.so.1.2 symlinked, none is being symlinked, so
it's bad in its current state.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libgl1-mesa-dev 10.3.0-0ubuntu3
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
BootLog: * Starting Deluge BitTorrent Daemon deluged
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Nov 10 19:40:31 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
fglrx-updates-core, 14.201, 3.16.0-23-generic, i686: installed
fglrx-updates-core, 14.201, 3.16.0-25-generic, i686: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8330] [1002:9832]
(prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems Device [1179:fa34]
Subsystem: Toshiba America Info Systems Device [1179:fa34]
InstallationDate: Installed on 2013-10-30 (376 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
LightdmGreeterLog: ** (lightdm-gtk-greeter:6257): WARNING **: Failed to load
user image: Failed to open file '/home/reslayer/.face': No such file or
directory
LightdmGreeterLogOld: ** (lightdm-gtk-greeter:5685): WARNING **: Failed to
load user image: Failed to open file '/home/reslayer/.face': No such file or
directory
MachineType: TOSHIBA Satellite C50D-A-K8K
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=384M-:128M
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M
vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.10
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: PT10AN
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias:
dmi:bvnInsydeCorp.:bvr1.10:bd05/22/2013:svnTOSHIBA:pnSatelliteC50D-A-K8K:pvrPSCH2R-00700JRU:rvnAMD:rnPT10AN:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C50D-A-K8K
dmi.product.version: PSCH2R-00700JRU
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 28 04:22:34 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1
xserver.video_driver: fglrx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1391243/+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 1391954] Re: indicator-sound not running on first boot
** Branch linked: lp:~ted/ubuntu-touch-session/indicator-sound- override-v2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “ubuntu-touch-session” package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1391954/+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 1392118] Re: two graphics adapter for the notebook
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1392118 Title: two graphics adapter for the notebook Status in “xorg” package in Ubuntu: New Bug description: dv6 notebook 3190sl (HP) there are two graphics adapters (AMD) , the first discrete ( HD5xxx Series) , the second for energy saving ( HD4xxx Series) ... The problem is that you can not use the discrete GPU , the GPU uses only ever HD4xxx energy saving is there a way to activate the first discrete graphics card and make it the default ? P.S.: there are no options in the bios. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Nov 13 01:07:23 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] [1002:9712] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1440] Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:1440] InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=9ce14554-fd5d-491c-8dc9-7a20db4be669 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/11/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.28 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1440 dmi.board.vendor: Hewlett-Packard dmi.board.version: 67.33 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.28:bd04/11/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn1440:rvr67.33:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058B11242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed Nov 12 23:10:56 2014 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1392118/+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 1391954] Re: indicator-sound not running on first boot
** Package changed: indicator-sound (Ubuntu) => ubuntu-touch-session (Ubuntu) ** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) => Ted Gould (ted) ** Changed in: ubuntu-touch-session (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1391954 Title: indicator-sound not running on first boot Status in “ubuntu-touch-session” package in Ubuntu: In Progress Bug description: Steps to reproduce: 1. Boot the device after a fresh flash with --wipe or --bootstrap 2. Complete the wizard steps 3. Check the indicators for the presence of the sound indicator Expected result: Sound indicator is present and running Actual result: Indicator is not present. There is a placeholder for it on the menu as shown in http://people.canonical.com/~brendan-donegan/indicator- sound.png Running 'status indicator-sound' shows it is stopped ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-sound 12.10.2+14.10.20141021~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 16:26:28 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-135345) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-session/+bug/1391954/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Description changed: - There doesn't seem to be any obvious way to force LightDM's VNC server - to listen on only specified interfaces, most notably localhost. This - creates a security issue, as the best and most secure way to access a - VNC server is through an SSH tunnel where the client will only connect - to its localhost on a particular port having all connections through the - tunnel to the server's localhost port. + [Impact] + The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). - If there is a proper way to do this or some sort of work-around, I would - be very interested in how to do so. As of right now, this makes - LightDM's VNC server unusable for me. + [Test Case] + 1. Enable the VNC server in LightDM in lightdm.conf: + [VNCServer] + enabled=true + listen-address=127.0.0.1 + 2. Start LightDM + With this setup you should only be able to make a local connection. + + [Regression potential] + Low. If the option is not set LightDM has the old behaviour. -- 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/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: In Progress Status in Light Display Manager 1.10 series: In Progress Status in Light Display Manager 1.12 series: In Progress Status in Light Display Manager 1.2 series: In Progress Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Precise: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Status in “lightdm” source package in Vivid: Triaged Bug description: [Impact] The XDMCP and VNC servers in LightDM allow connections on any network interface. It is desirable for these to be limited to a particular interface to limit who can connect (i.e. only allow local connections on 127.0.0.1). [Test Case] 1. Enable the VNC server in LightDM in lightdm.conf: [VNCServer] enabled=true listen-address=127.0.0.1 2. Start LightDM With this setup you should only be able to make a local connection. [Regression potential] Low. If the option is not set LightDM has the old behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
To be clear: I removed the file before rebooting, but it got regenerated and refilled at a furious pace, with the same message: _xgeWireToEvent: Unknown extension 148, this should never happen. At that time, "top" was reporting upstart as the most process, obviously caught in an infinite loop throwing this erroor about the extension 148. It seems like this is the bug: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1369113 And it seems that the spamming, at least, would be removed with an upgrade of libXext to 1.3.3. Or at least, it would be nice to backport the relevant patch http://patchwork.freedesktop.org/patch/22124/ -- 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 1190344] Re: lightdm is leaking FDs -fix
** Description changed:
- Description of problem:
- Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
+ [Impact]
+ LightDM doesn't close the server side end of the pipes used to communicate
with session processes. This means each session that is created leaks two file
descriptors eventually leading to the system stopping it from creating new
pipes.
- Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
- Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
- Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
+ [Test Case]
+ 1. Start LightDM
+ 2. Check how many pipes are open
+ # lsof -p {lightdm_pid} | grep FIFO | wc -l
+ 3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
+ 4. Check how many pipes exist using step 2.
+ Expected result:
+ No more pipes should be open
+ Observed result:
+ Many pipes remain open
-
- Tested on:
- Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
-
- Steps to Reproduce:
-
- 1. login on a console and find the pid of main lightdm process then:
- # lsof -p {lightdm_pid} |grep FIFO |wc -l
- 26
-
- 2. switch to X console and login through lightdm and then logout
-
- 3. go back on comsole
- # lsof -p {lightdm_pid} |grep FIFO |wc -l
- 32
-
- Here is a patch that fixes the issue. It may have several lines offset
- because we use modified lightdm but it is good for the original version
- too.
-
- regards,
- Rumen
+ [Regression Potential]
+ Low. Fix is to close pipes when finished with them. Tested with regression
tests.
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Fix Released
Status in Fedora:
Unknown
Bug description:
[Impact]
LightDM doesn't close the server side end of the pipes used to communicate
with session processes. This means each session that is created leaks two file
descriptors eventually leading to the system stopping it from creating new
pipes.
[Test Case]
1. Start LightDM
2. Check how many pipes are open
# lsof -p {lightdm_pid} | grep FIFO | wc -l
3. Create sessions by either cycling between users in Unity Greeter or
logging in and out
4. Check how many pipes exist using step 2.
Expected result:
No more pipes should be open
Observed result:
Many pipes remain open
[Regression Potential]
Low. Fix is to close pipes when finished with them. Tested with regression
tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1392128] [NEW] Missing training tutorials and documents for HTML 5 development
Public bug reported: We are going to have our developer contest soon next month (Dec). We need to come out the detailed training materials for the HTML 5 development. We will not have any on-site training, instead we need to make sure that developers will get all of the needed info in their development. - The HTML 5 tutorials on HTML development are outdated since they were based on the old platform. They need to be updated - We need a document in high level to tell why a developer should choose the Cordova APIs or HTML 5 to start to development in the very beginning in view of the fact that we provide two ways of development. The document needs to be translated into Chinese once it is ready - More documents and tutorials/examples for Ubuntu specific APIs at http://developer.ubuntu.com/api/html5/development/. It would be good to have the offline document inside the SDK as well. - A tutorial on how to do Cordova API HTML 5 app providing an entry on our developer website. Currently, there are many versions of Cordova APIs there on the Cordova official website. We need clearly tell the developer which version to go. - A video introduction about our offering about HTML 5 development. Thanks & best regards, XiaoGuo ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: univ-train ** Tags added: univ-train -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1392128 Title: Missing training tutorials and documents for HTML 5 development Status in “webbrowser-app” package in Ubuntu: New Bug description: We are going to have our developer contest soon next month (Dec). We need to come out the detailed training materials for the HTML 5 development. We will not have any on-site training, instead we need to make sure that developers will get all of the needed info in their development. - The HTML 5 tutorials on HTML development are outdated since they were based on the old platform. They need to be updated - We need a document in high level to tell why a developer should choose the Cordova APIs or HTML 5 to start to development in the very beginning in view of the fact that we provide two ways of development. The document needs to be translated into Chinese once it is ready - More documents and tutorials/examples for Ubuntu specific APIs at http://developer.ubuntu.com/api/html5/development/. It would be good to have the offline document inside the SDK as well. - A tutorial on how to do Cordova API HTML 5 app providing an entry on our developer website. Currently, there are many versions of Cordova APIs there on the Cordova official website. We need clearly tell the developer which version to go. - A video introduction about our offering about HTML 5 development. Thanks & best regards, XiaoGuo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1392128/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm Status: Fix Released => Triaged ** Changed in: lightdm Milestone: 1.13.0 => 1.13.1 ** Changed in: lightdm/1.10 Milestone: 1.10.4 => 1.10.5 ** Changed in: lightdm/1.12 Milestone: 1.12.2 => 1.12.3 ** Changed in: lightdm/1.2 Milestone: 1.2.9 => 1.2.10 ** Changed in: lightdm/1.2 Status: Fix Released => In Progress ** Changed in: lightdm/1.10 Status: Fix Released => In Progress ** Changed in: lightdm/1.12 Status: Fix Released => In Progress ** Changed in: lightdm Status: Triaged => In Progress -- 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/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: In Progress Status in Light Display Manager 1.10 series: In Progress Status in Light Display Manager 1.12 series: In Progress Status in Light Display Manager 1.2 series: In Progress Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Precise: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Status in “lightdm” source package in Vivid: Triaged Bug description: There doesn't seem to be any obvious way to force LightDM's VNC server to listen on only specified interfaces, most notably localhost. This creates a security issue, as the best and most secure way to access a VNC server is through an SSH tunnel where the client will only connect to its localhost on a particular port having all connections through the tunnel to the server's localhost port. If there is a proper way to do this or some sort of work-around, I would be very interested in how to do so. As of right now, this makes LightDM's VNC server unusable for me. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1310316] Re: Text scaling factor changing unexpectedly
I don't have the tweak tool installed. I'm using HiDPI hardware. I set
the scale to 1.12 in the display preferences option, and each time I
start unity (or run "setsid unity") the font increases in size. It seems
that in the display preferences, it needs to be set to 1.0 for the
constant font size changing to not occur. I've therefore set this back
to 1.0, and instead set up a start-up script to "gsettings set
com.ubuntu.user-interface scale-factor "{'eDP1': 10}"" instead.
--
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/1310316
Title:
Text scaling factor changing unexpectedly
Status in Unity:
Confirmed
Status in “unity” package in Ubuntu:
Incomplete
Bug description:
I have a MacBook pro with a Retina display. I have set the "Scale for
menu and title bars" setting (into Settings > Displays) to 1.5 to
make the UI looks good on my screen. That works very well. But
sometimes, usually after logging, all the fonts of the UI become much
bigger.
When that happen I open unity tweat tool and notice that the text
scaling factor changed to 2.25. If I reset it to 1 the all the fonts
go back to normal.
The problem does not happen all the time. I would say it happen one
time out of three logging. It may also happen when installing
applications from the software center. I have yet to find a procedure
to reproduce it all the times.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30
PST 2014
GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Apr 20 18:21:02 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed
bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed
nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed
GraphicsCard:
NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Apple Inc. Device [106b:00f2]
InstallationDate: Installed on 2014-04-19 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac
(20140417)
MachineType: Apple Inc. MacBookPro10,1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic
root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-C3EC7CD22292981F
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-C3EC7CD22292981F
dmi.modalias:
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
dmi.product.name: MacBookPro10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.10-1ubuntu2
xserver.bootTime: Sun Apr 20 18:04:05 2014
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.15.1-0ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug
[Touch-packages] [Bug 1317253] Re: UI scaling and font scaling sometime get confused/change at random.
*** This bug is a duplicate of bug 1310316 *** https://bugs.launchpad.net/bugs/1310316 To reproduce this issue, simply type "setsid unity" from the command line to see the font size keep deviating from the desired size. Running, "gsettings set com.canonical.Unity.Interface text-scale-factor 1.25" will restore the size to 1.25, for example, if that is the desired size. -- 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/1317253 Title: UI scaling and font scaling sometime get confused/change at random. Status in Unity: New Status in Unity Tweak Tool: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the "Text Scaling Factor" having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317253/+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 1317253] Re: UI scaling and font scaling sometime get confused/change at random.
*** This bug is a duplicate of bug 1310316 *** https://bugs.launchpad.net/bugs/1310316 Ditto what ~james-fsck says. The problem is that the adjustment above or below 1.0 is incremented each time unity resets, so if someone chose smaller, it keeps getting smaller, or if someone chooses bigger, the font keeps getting bigger. The tweak tool is a temporarily workaround, but the problem is in the way the display preferences interacts with the font sizes - i.e. it keeps re-applying the change. -- 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/1317253 Title: UI scaling and font scaling sometime get confused/change at random. Status in Unity: New Status in Unity Tweak Tool: Invalid Status in “unity” package in Ubuntu: Confirmed Bug description: I have a Lenovo Yoga 2 Pro, with a 13.3" screen running at 3200x1800 pixels... I bought this partly to test out the UI scaling in Unity!... and I have to say it's very awesome (both the screen and the UI scaling)... however I have encountered a strange problem. Seemingly at random, I have so far 3 times in 10 days had the font size (not UI size) suddenly jump to something much too large. UI scaling for the display is set at 1.38x and this is quite perfect for me, it sure means no one will be able to read my screen over my shoulder, but I that's fine! I had to install a Firefox plugin to apply scaling there, but I realise why that is. Anyway... I installed ubuntu-tweak and discovered that the large fonts were due to the "Text Scaling Factor" having jumped up to a number above 2.5... I also discovered that I could not move the slider because every time I moved it the fonts re-scaled the slider moved and lost mouse focus... and the slider reset to where it was to begin with... I clicked the button on the right to return to 1.0, and it returned to 1.4, which I assume is representative of the 1.38 I set in the screen scaling... but I have no explanation for why it suddenly jumped (when I logged out and back in) from 1.4 to something like 2.5.).. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed May 7 20:55:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317253/+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 1190344] Re: lightdm is leaking FDs -fix
This bug was fixed in the package lightdm - 1.13.0-0ubuntu1
---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium
* New upstream release:
- Fix crash when having configuration keys defined in multiple places
(LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
(LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
* debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
~/.profile etc (LP: #678421)
-- Robert AncellThu, 13 Nov 2014 11:08:17
+1300
** Changed in: lightdm (Ubuntu Vivid)
Status: Triaged => Fix Released
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Fix Released
Status in Fedora:
Unknown
Bug description:
Description of problem:
Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Tested on:
Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
Steps to Reproduce:
1. login on a console and find the pid of main lightdm process then:
# lsof -p {lightdm_pid} |grep FIFO |wc -l
26
2. switch to X console and login through lightdm and then logout
3. go back on comsole
# lsof -p {lightdm_pid} |grep FIFO |wc -l
32
Here is a patch that fixes the issue. It may have several lines offset
because we use modified lightdm but it is good for the original
version too.
regards,
Rumen
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 678421] Re: Error message for a faulty ~/.profile script
This bug was fixed in the package lightdm - 1.13.0-0ubuntu1
---
lightdm (1.13.0-0ubuntu1) vivid; urgency=medium
* New upstream release:
- Fix crash when having configuration keys defined in multiple places
(LP: #1377373)
- Fix pipe file descriptor leak for each session login / authentication
(LP: #1190344)
- Use correct syntax for DesktopNames key in session files (LP: #1383321)
- Match seat configuration with globbing (LP: #1364911)
- Allow user switching in multi-seat until bug stopping greeter showing on
logout is fixed
- Disable log message when AccountsService users change (LP: #1376357)
- Update AppArmor scripts, requires AppArmor 2.9
- Update tests to run better on servers
* debian/config-error-dialog.sh:
- Show warning dialog instead of interrupted login if syntax error in
~/.profile etc (LP: #678421)
-- Robert AncellThu, 13 Nov 2014 11:08:17
+1300
** Changed in: lightdm (Ubuntu)
Status: In Progress => Fix Released
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
Fix Released
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
In Progress
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in ".profile"
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user ".profile" and ".xprofile" scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+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 1364911] Re: Support globbing in seat config sections
This bug was fixed in the package lightdm - 1.13.0-0ubuntu1 --- lightdm (1.13.0-0ubuntu1) vivid; urgency=medium * New upstream release: - Fix crash when having configuration keys defined in multiple places (LP: #1377373) - Fix pipe file descriptor leak for each session login / authentication (LP: #1190344) - Use correct syntax for DesktopNames key in session files (LP: #1383321) - Match seat configuration with globbing (LP: #1364911) - Allow user switching in multi-seat until bug stopping greeter showing on logout is fixed - Disable log message when AccountsService users change (LP: #1376357) - Update AppArmor scripts, requires AppArmor 2.9 - Update tests to run better on servers * debian/config-error-dialog.sh: - Show warning dialog instead of interrupted login if syntax error in ~/.profile etc (LP: #678421) -- Robert AncellThu, 13 Nov 2014 11:08:17 +1300 ** Changed in: lightdm (Ubuntu) Status: Fix Committed => Fix Released -- 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/1364911 Title: Support globbing in seat config sections Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Bug description: Add support for simple globbing in seat config sections. Example: if a config section [Seat:seatFoo*] is available in lightdm.conf, it will match any seat name starting with "seatFoo", like "seatFooBar", "seatFooBaz", etc. In particular, [Seat:seat*] will match any seat added from logind (including seat0), and [Seat:*] will match any seat (including those eventually added from other mechanisms than logind), just as [SeatDefaults] currently does. It was already merged into trunk in revision 2040, but has been reverted in revision 2042 due to some unexpected problem, so I'm opnening this bug report to keep track of changes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1364911/+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 1383321] Re: Support XDG DesktopNames field in session files
This bug was fixed in the package lightdm - 1.13.0-0ubuntu1 --- lightdm (1.13.0-0ubuntu1) vivid; urgency=medium * New upstream release: - Fix crash when having configuration keys defined in multiple places (LP: #1377373) - Fix pipe file descriptor leak for each session login / authentication (LP: #1190344) - Use correct syntax for DesktopNames key in session files (LP: #1383321) - Match seat configuration with globbing (LP: #1364911) - Allow user switching in multi-seat until bug stopping greeter showing on logout is fixed - Disable log message when AccountsService users change (LP: #1376357) - Update AppArmor scripts, requires AppArmor 2.9 - Update tests to run better on servers * debian/config-error-dialog.sh: - Show warning dialog instead of interrupted login if syntax error in ~/.profile etc (LP: #678421) -- Robert AncellThu, 13 Nov 2014 11:08:17 +1300 ** Changed in: lightdm (Ubuntu Vivid) Status: Fix Committed => Fix Released -- 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/1383321 Title: Support XDG DesktopNames field in session files Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: Fix Committed Status in “lightdm” source package in Utopic: Fix Committed Status in “lightdm” source package in Vivid: Fix Released Bug description: [Impact] LightDM doesn't support the XDG standard "DesktopNames" field in session .desktop files. Instead we only support X-LightDM-DesktopName which was used before the standard was set. Newer sessions might expect DesktopNames to work. [Test Case] 1. Install a session which has DesktopNames set in /usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity; 2. Start this session Expected result: XDG_CURRENT_DESKTOP is set to GNOME:Unity Observed result: XDG_CURRENT_DESKTOP is not set [Regression Potential] Low. This feature is only activated if the field is set. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1383321/+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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
Ok, before rebooting, I just removed the offending file. It is growing at a rate of 1Gb every 10s or so. I will try logging out and in, and see if the log is still growing continuously ... -- 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 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
It just happened here. I will need to clean up and reboot. This is how it looks like lmilano@grisell:upstart$ ls -lh unity7.log -rw-r- 1 lmilano users 53G Nov 12 16:03 unity7.log lmilano@grisell:upstart$ tail unity7.log _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 148, this should never happen. _xgeWireToEvent: Unknown extension 1lmilano@grisell:upstart$ -- 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 1317449]
*** Bug 340792 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1317449 Title: sqlite3 version 3.8.2 breaks digikam Status in digiKam - digital photo management: Won't Fix Status in SQLite: Won't Fix Status in “digikam” package in Ubuntu: Fix Released Status in “sqlite3” package in Ubuntu: Fix Released Status in “digikam” source package in Trusty: Confirmed Status in “sqlite3” source package in Trusty: Confirmed Status in “digikam” source package in Utopic: Fix Released Status in “sqlite3” source package in Utopic: Fix Released Bug description: Please update sqlite to a version > 3.8.2. According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 3.8.2 causes crashes in digikam (and possibly other software) in various situations. Several reports confirm, that versions > 3.8.2 fix the issue. I'm using the 3.8.4.3 package from debian testing right now and can't trigger crashes anymore. Workaround: Install sqlite3 > 3.8.2, e.g. you can manually install the corresponding deb packages from either utopic or debian. To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/1317449/+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 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites
I am also experiencing this issue couple of times every day. Music in background keeps on playing and I can move mouse pointer, but everything else on screen is frozen. Usually if I wait around 30 seconds or if I switch to tty1 and back to tty7 it also usually solves the problem. Also I should note that when I press Ctrl+Alt+1 there is couple of second delay before showing the terminal. I am using dual monitor setup and integrated Intel graphics chip: #lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) -- 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/1314871 Title: Ubuntu 14.04 random screen freeze while Normal OS activites Status in “xorg” package in Ubuntu: Confirmed Bug description: same symptom described in https://bugs.launchpad.net/ubuntu/+source /xorg-server/+bug/1184451 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 1 09:21:51 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] InstallationDate: Installed on 2014-04-27 (3 days ago) InstallationMedia: Ubuntu-Kylin 14.04 LTS "Trusty Tahr" - Release amd64 (20140417.1) MachineType: Dell Inc. Vostro 3400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RXV7H dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3400 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871/+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 1391909] Re: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked
*** This bug is a duplicate of bug 1391522 *** https://bugs.launchpad.net/bugs/1391522 ** This bug has been marked a duplicate of bug 1391522 tel:/// URLs dispatched when phone is locked are not respected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1391909 Title: Caller number not loaded in dialler when Call Back or phone icon is clicked in missed call notification and the device is locked Status in “dialer-app” package in Ubuntu: New Status in “unity8” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Place a call to the device and hang up on the other end (to generate a missed call notification) 2. Ensure the greeter is locked 3. Swipe down on the notifications indicator (message icon) 4. Tap on the missed call 5. Tap on Call Back 6. Unlock the screen Expected result: Dialler application opens with the number loaded ready to call Actual result: Dialler application opens but the number is not loaded N.B. At step 4 we can tap on the phone icon in the missed call notification to get the same effect, it appears to be functionally equivalent to the Call Back button ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-messages 13.10.1+14.10.20141007-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 12 14:50:42 2014 InstallationDate: Installed on 2014-11-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141112-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391909/+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 1391522] Re: tel:/// URLs dispatched when phone is locked are not respected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dialer-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1391522 Title: tel:/// URLs dispatched when phone is locked are not respected Status in “dialer-app” package in Ubuntu: Confirmed Bug description: Steps to reproduce: * have a passcode-locked phone * run: $ gdbus call -e -d com.canonical.URLDispatcher -o /com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 'tel:///1234' '' * type the passcode Expected: * dialer opens with 1234 typed in the number box Current: * dialer opens blank or with 1234 that resets to blank a split second later ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20141106-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Tue Nov 11 14:29:21 2014 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (2014-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391522/+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 1081590] Re: could not determine source package name
** Also affects: apport Importance: Undecided Status: New ** No longer affects: apport -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1081590 Title: could not determine source package name Status in “apport” package in Ubuntu: New Status in “cups” package in Ubuntu: New Bug description: When I open/switch on HP printer PSC 750 to print I get an error message and a request to send a report, which I accept. The following message is then displayed "Could not determine the package or source package name." This happens every time I try to print from Internet or Libre office programmes. I therefore do not know if the bug gets reported or the error report message is just terminated because of lack of information gleaned from my system. What should I do? Printing itself does not appear to be affected. Problem only occurs in 12.04. It was not a problem in 10.04 Regards Rodger To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1081590/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: debconf (Ubuntu) Assignee: (unassigned) => erick samonte (erick-samonte4) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Ambasa Operating System: New Status in Debconf: New Status in “aptdaemon” package in Ubuntu: Triaged Status in “debconf” package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+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 1043627] Re: [SRU] Add XIM Support to Nux
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1043627 Title: [SRU] Add XIM Support to Nux Status in Nux: Fix Released Status in Nux 2.0 series: Fix Committed Status in Unity: Fix Released Status in Unity 5.0 series: Fix Committed Status in “nux” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Fix Released Status in “nux” source package in Quantal: Won't Fix Status in “unity” source package in Quantal: Won't Fix Status in “nux” source package in Raring: Confirmed Status in “unity” source package in Raring: Fix Committed Bug description: [Impact] As 12.04 is an LTS, many users decide to stay with that version until the next LTS version is available. Many of those users require different input methods to comfortably input characters in their language. We do support IBus for some of the languages, but others are still using XIM as the input framework. Those users cannot input in their language using their standard input methods. This means using the Dash and HUD is much more troublesome or even impossible in normal cases. We think that even though it is essentially a new feature, it can be thought that the lack of support for non-IBus additional input methods is a bug in a way. It is a big change, but with proper testing, we would ensure that the addition does not introduce any new regressions. This addition would make many MANY users happy, which can be seen at least by the number of affected people in LP: #983254. Also, the change is needed by OEM. It is a big change, but it's crucial for CJK - Kyrlin has voiced the proposition to use fctix as the default input method, which _needs_ XIM support in Nux and Unity. [Test Case] 1. Install fctix-pinyin 2. Run im-config and enable fctix as the default IM 3. Reboot your machine 4. Open the dash and input non-latin characters using fctix -> Non latin characters (Chinese in this case) should appear on screen. [Regression Potential] In an impossible scenariu, broken IBus input or input in overall in Nux input fields. The good thing about the XIM support is that it's rather isolated, so potential breakage of the XIM code won't impact normal Nux workflow. Just XIM input might not work. The author of the code, Brandon, also mentions that new regression potential is low as the XIM code is not being used by default. As XIM is not the default, when IBus is present - without explicitly setting XIM in im-config, the XIM parts are not even accessed. [Other Info] The same functionality is already available in the newer Unity releases. Original description: Right now the only input method (IM) that works with Unity/Nux is IBus. This means anyone who uses a different IM would have to switch to IBus in order to type in their language. This is something that needs to be fixed and will make Unity/Nux friendlier to those who use different IMs. If you do not use an IM then this will not affect you. XIM was the very first IM framework for the X window system, which means most IMs are supported by it. A List of IMs that will be supported by this branch (There could be more): http://en.wikipedia.org/wiki/List_of_input_methods_for_UNIX_platforms All of those under XIM will now work in Unity and Nux with this branch. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1043627/+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 1034616] Re: [Regression] Lowering window by middle click doesn't switch focus to raised window
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1034616 Title: [Regression] Lowering window by middle click doesn't switch focus to raised window Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Unity: Fix Released Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Middle mouse click on title bar will lower window; but it does not switch the focus to the window which was raised above it. 1) Open a gedit app window 2) Open a calc app 3) Middle click the mouse on the calculator title bar. It should lower the calculator and raise the gedit window as well as switch the focus to gedit. But it doesnt switch the focus. See also: autopilot run unity.tests.test_panel.PanelGrabAreaTests.test_lower_the_maximized_window_works To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1034616/+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 1011120] Re: Desktop Cube: Unity's top panel shadow gets deformed also and rendered on the desktop cube instead of sticking with the top panel when the cube gets activated
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1011120 Title: Desktop Cube: Unity's top panel shadow gets deformed also and rendered on the desktop cube instead of sticking with the top panel when the cube gets activated Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The shadow of the main Unity panel on top should stay untouched, like the panel does, when using the desktop cube, instead of being rendered onto the cube. The situation gets even worse visually when "Cube Reflection and Deformation" is used additionally, because now the shadow does not deform with the cube, but stays in the same position of the original cube. Ubuntu 12.04, Compiz 0.9.7.8-0ubuntu1vvpreproposed2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1011120/+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 1059601] Re: [dash] Rendering flaw of ghost icons when a preview is open.
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1059601 Title: [dash] Rendering flaw of ghost icons when a preview is open. Status in Unity: Fix Released Status in Unity 6.0 series: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: See the icon in the top-left corner of the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059601/+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 1059759] Re: Clicking on Workspace Switcher icon when the expo is showing, not always closes it
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1059759 Title: Clicking on Workspace Switcher icon when the expo is showing, not always closes it Status in Unity: Fix Released Status in Unity 6.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Especially in multimonitor: 1) Click on the workspace switcher icon 2) The expo is shown 3) Click again on the workspace switcher icon Expected result: 4) The expo is hidden Actual result: 4) Expo is not hidden always (repeat this for all the monitors) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1059759/+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 1062316] Re: Glow border for selected window in scale mode does not draw correctly on the top corners
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1062316 Title: Glow border for selected window in scale mode does not draw correctly on the top corners Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: See the attached screenshot: the glow is not correctly applied to the top corners To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1062316/+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 1181367] Re: Alt+Tab switches between incorrect windows after some time of activity
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1181367 Title: Alt+Tab switches between incorrect windows after some time of activity Status in Unity: Fix Released Status in Unity 7.0 series: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Raring: Fix Released Bug description: [Impact] Due to overflow, alt+tab between the same application becomes impossible] [Test Case] 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. [Regression Potential] Low, types extended from int to long long. The code affected is the alt tab functionality. Due to an overflow, after some time of activity it's impossible to alt+tab between two windows of the same application. 1) Keep two windows of an app (say terminal) opened for some time, and another window of a different app 2) Focus one window terminal keeping the other terminal window below it 3) Press Alt+Tab Expected behavior 4) The other terminal window is focused Actual behavior: 4) Other opened application is selected instead. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1181367/+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 1046125] Re: Decoration in spread windows should use the system font
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1046125 Title: Decoration in spread windows should use the system font Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: As title says. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1046125/+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 1283453] Re: window spread with too narrow titlebars on hig-dpi screen
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1283453 Title: window spread with too narrow titlebars on hig-dpi screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Titlebars are currently cropped and don't completely display the text in spread mode, if the global scaling factor is set to 2. org.gnome.desktop.interface.scaling-factor = 2 org.gnome.desktop.interface.text-scaling-factor = 1.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 22 15:04:07 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (19 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1283453/+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 1162886] Re: test-gtest [ FAILED ] TestIconLoader.TestGetManyIcons - segfaults at times.
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1162886 Title: test-gtest [ FAILED ] TestIconLoader.TestGetManyIcons - segfaults at times. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Stack trace: http://paste.ubuntu.com/5668678/ Full stack trace: http://paste.ubuntu.com/5668696/ Run: ./test-gtest --gtest_filter=*GetManyIcons* It also passes at times as well. *Update* I also just got this while restarting unity...so this seems a bit more serious then a failing unit test: http://paste.ubuntu.com/5667999/ I got it after doing a compiz --replace ccp, then opening the dash...though I can't reproduce it :(. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1162886/+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 1097991] Re: Port to new barrier event API
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: unity (Ubuntu Raring) Status: Fix Committed => Fix Released -- 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/1097991 Title: Port to new barrier event API Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Raring: Fix Released Bug description: The pointer barrier event API we've patched in to libXfixes has moved upstream in Xserver 1.14. However, the API has changed. The barrier events and pointer release API is now in the input lib, libXi as of version 1.6.99.1 . It should be reasonably easy to port to the new API: Peter Hutterer's blog post¹ describes how to use it. The main differences are that you need to add the barrier event mask to the XI event mask, rather than window event mask, and that it now uses generic events, so you need to allocate the event data before using it and free the event data after using it XGetEventData/XFreeEventData. ¹: http://who-t.blogspot.com.au/2012/12/whats-new-in-xi-23-pointer- barrier.html To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1097991/+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 1117500] Re: test-unit needs to be ported to gtest
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- 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/1117500 Title: test-unit needs to be ported to gtest Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Test-unit uses glib testing framework. It needs to be ported to gtest (google test). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1117500/+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 1207669] Re: [MIR] Need binary package included in main.
** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: unity Status: Fix Committed => Fix Released -- 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/1207669 Title: [MIR] Need binary package included in main. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: This source package is already in main, but in preparation for https://bugs.launchpad.net/bugs/1206268 I will need binary package unity-autopilot included in main as well. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1207669/+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 864037] Re: workspace switcher zoom failure with multiple monitors
** Changed in: unity (Ubuntu) Status: In Progress => Fix Released -- 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/864037 Title: workspace switcher zoom failure with multiple monitors Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Oneiric: Fix Released Bug description: SRU TEST CASE: 1. connect an external display to your system 2. click workspace switcher 3. notice all the graphical problems on the screen 4. now install Unity from oneiric-proposed 5. Notice everything is working as it with single display =Original Report= When my laptop is not connected to an external monitor and I click the Workspace Switcher, the "zoom out" effect to show all workspaces works properly. When I connect a monitor to my DisplayPort output and click Workspace Switcher, the laptop's built-in monitor shows a messed-up background (see attachment) and the external monitor shows no background. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,snap,grid,mousepoll,compiztoolbox,resize,imgpng,wall,unitymtgrabhandles,regex,gnomecompat,place,vpswitch,move,animation,workarounds,expo,session,ezoom,fade,scale,unityshell] CompositorRunning: compiz Date: Sat Oct 1 07:38:07 2011 DistUpgraded: Fresh install DistroCodename: oneiric DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:172a] InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2) MachineType: Hewlett-Packard HP EliteBook 8440p PccardctlIdent: Socket 0: product info: "RICOH", "Bay8Controller", "", "" manfid: 0x, 0x function: 254 (unknown) PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=26780926-1f18-4056-ae79-bf1656287393 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CCU Ver. F.02 dmi.board.name: 172A dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 30.29 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CCUVer.F.02:bd12/22/2009:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.29:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8440p dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/864037/+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 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites
I'm experiencing the same issue but I'm able to move mouse pointer. >From time to time I'm switching between single and dual-monitor configuration on my laptop with dual video (Lenovo V580) and I'm observing alike screen freezing which takes about half of minute. I/O led does not show heavy activity and it looks like background processes are working (at least music is playing). # lspci -v | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller]) 01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 645M] (rev ff) (prog-if ff) Video Driver: "NVIDIA binary driver - version 331.38 from nvidia-331 (proprietary, tested)" PRIME Profile settings - Intel (Power Saving Mode) -- 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/1314871 Title: Ubuntu 14.04 random screen freeze while Normal OS activites Status in “xorg” package in Ubuntu: Confirmed Bug description: same symptom described in https://bugs.launchpad.net/ubuntu/+source /xorg-server/+bug/1184451 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu May 1 09:21:51 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] InstallationDate: Installed on 2014-04-27 (3 days ago) InstallationMedia: Ubuntu-Kylin 14.04 LTS "Trusty Tahr" - Release amd64 (20140417.1) MachineType: Dell Inc. Vostro 3400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RXV7H dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3400 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871/+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 1310101] Re: bluetooth icon doesnt dim when disabled in xubuntu 14.04
It seems also that this particular problem was seen since the introduction of blueman-applet 1.23, which is the current in xubuntu 14.04. http://kissmyarch.blogspot.it/2011/10/blueman-applet-with- missing-icon.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1310101 Title: bluetooth icon doesnt dim when disabled in xubuntu 14.04 Status in “indicator-bluetooth” package in Ubuntu: Confirmed Bug description: During the live cd and after the installation, when i disable bluetooth, the bluetooth icon in the panel doesnt dim as it does with other distros, including ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1310101/+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 678421] Re: Error message for a faulty ~/.profile script
I've removed the tasks on LightDM (the project) as the fixes for this
were all in debian/.
** No longer affects: lightdm/1.12
** No longer affects: lightdm/1.10
** No longer affects: lightdm
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
In Progress
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in ".profile"
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user ".profile" and ".xprofile" scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+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 1172649] Re: Spotify icon is displayed twice in Unity Launcher
** Changed in: unity (Ubuntu) Importance: Undecided => Medium -- 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/1172649 Title: Spotify icon is displayed twice in Unity Launcher Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 13.04 and latest Spotify version. The spotify icon (when the application is not running) it's sticked on the launcher, and this is ok. When I click on it, another icon appears (see the attached picture). This happened also in older versions of Unity. Could someone please fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1172649/+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 1392095] [NEW] Sync libcap2 1:2.24-6 (main) from Debian unstable (main)
Public bug reported: Please sync libcap2 1:2.24-6 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * 0004-include-sys-xattr.patch: Include sys/xattr.h in sys/capability.h * 0004-include-sys-xattr.patch: Include sys/xattr.h in sys/capability.h * 0004-include-sys-xattr.patch: Include sys/xattr.h in sys/capability.h * New upstream release. - Drop 0001-Add-CAP_WAKE_ALARM-and-CAP_BLOCK_SUSPEND-to-capabili.patch, included upstream. * Add patch (which has been forwarded to the upstream maintainer) to define new capabilities in most recent kernels. (LP: #1084000) (Closes: #689035) * Add patch (which has been forwarded to the upstream maintainer) to define new capabilities in most recent kernels. (LP: #1084000) (Closes: #689035) * Add patch (which has been forwarded to the upstream maintainer) to define new capabilities in most recent kernels. (LP: #1084000) (Closes: #689035) * Resynchronise with Debian. Remaining changes: - Support cross-building. 0003-refine-setcap-error-message.patch -> 0002-setcap-error-message.patch 0004-include-sys-xattr.patch -> 0003-include-sys-xattr.patch Cross-building is now supported by Debian, but has been re-worked. Changelog entries since current vivid version 1:2.24-0ubuntu2: libcap2 (1:2.24-6) unstable; urgency=medium * debian/rules: - Use proper assignment for CC. It has a default value, so ?= assignment does not make sense. Using := fixes a FTCBFS. Thanks, Helmut Grohne. Closes: #762575 * debian/control: - Add XS-Testsuite for autopkgtest * debian/tests/executables: - Add an autopkgtest for getcap(8) and setcap(8) functionality -- Christian Kastner Thu, 25 Sep 2014 01:41:47 +0200 libcap2 (1:2.24-5) unstable; urgency=medium * debian/libcap2-bin.lintian-overrides: - Drop this file; it only contained an unused lintian override for statically-linked-binary * debian/control: - Bump Standards-Version to 3.9.6 (no changes needed) - Add binary package libcap2-dbg for debugging symbols * debian/rules: - Use dpkg/architecture.mk instead of manual assignment - Rework the cross-compiling support. Less code, and less assumptions about the environment - Create dirs in override_dh_installdirs - Simplify installation stage - Add override_dh_strip to place symbols in libcap2-dbg * Package libcap-dev: - Move the static library from /lib/ to /usr/lib/, where development files belong according to the FHS. /lib/ is only for essential shared libraries. * debian/TODO: - Drop file (all items were either dropped or completed) -- Christian Kastner Fri, 19 Sep 2014 13:52:51 +0200 libcap2 (1:2.24-4) unstable; urgency=low * debian/control: - Set myself to maintainer. Closes: #756091 - Drop redundant Section - Drop redundant Priority fields - Add Multi-Arch field for libcap2-bin - Point Vcs-* URLs to collab-maint * debian/rules: - Drop dh_builddeb override, xz is now default - Drop override_dh_makeshlibs; a symbols file is provided now * debian/copyright: - Add myself - Add missing copyright for manpages - Add missing copyright for contrib/* * debian/symbols: - Create symbols file * debian/watch: - Create watch file * debian/manpages: - Fix typo in manpage name (getcaps -> getpcaps) - Drop capsh.8, upstream ships capsh.1 now * debian/source/options: - Remove, as xz is now the default compression algo * debian/patches (refreshed): - Update headers to play more nicely with gbp-pq * debian/patches (added): - 0004-Don-t-hardcode-build-flags Needed so that hardening flags get honored - 0005-Syntax-fixes-for-man-pages -- Christian Kastner Sat, 26 Jul 2014 20:06:24 +0200 libcap2 (1:2.24-3) unstable; urgency=medium * I don't care anymore, not worth it.. orphaning. -- Daniel Baumann Fri, 25 Jul 2014 20:51:41 +0200 libcap2 (1:2.24-2) unstable; urgency=low * Adding provides for libcap2-dev that got lost during rebase (Closes: #79). -- Daniel Baumann Tue, 22 Jul 2014 10:55:23 +0200 libcap2 (1:2.24-1) unstable; urgency=low * Merging upstream version 2.24 (Closes: #734633): - in sync with current kernels (Closes: #689035) * Dropping unused orig-tar.sh. * Marking package as linux-any only (Closes: #745186). * Moving local manpages to subdirectory. * Applied patch from Loïc Minier to fix cross- building by passing CC and BUILD_CC to dh_auto_make, based on a patch by Colin Watson for the previous CDBS packaging, but adapted for the new dh-based packaging (Closes: #645908). * Adding manpages for capability.conf, getcaps, and pam_cap from Scott Schaefer (Closes: #504606). * Using xz explizitly for source tarballs. * Adding dpkg-source local options to abort on upstream changes. * Moving local pam-configs to local subdirectory. * Dropping watch file. *
[Touch-packages] [Bug 1391521] Re: can't type accented letters in ubuntu 14.10 [ast]
** Changed in: unity (Ubuntu) Importance: Undecided => High -- 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/1391521 Title: can't type accented letters in ubuntu 14.10 [ast] Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, after a fresh install of Ubuntu 14.10, ( and repositories proposed, and backports enabled ) , and a full update, it's impossible to use/type/write accented letters in Asturian languages. I've tested in other languages and this issue is not present. If user choose Asturian language, and Asturian keyboard, it's impossible to type á,é,í,ó,ú, ü, ñ. Steps to reproduce it: 1- Change language to Asturian 2- Change keyboard (Launcher-->System settings-->Text entry-->Asturian (Spain, with bottom-dot H and bottom-dot L). 3- Add it. 4- In the top panel, clic and select the text entry: Asturian 5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ (it will doesn't work) (if language system is another one, all keyboards works. If we choose Asturian, no one keyboard works, and is not possible to use accents) I thought this bug was related to: https://bugs.launchpad.net/unity/+bug/1330041 but we think they are different issues. Anyway, this bug has high importance for Asturian users, because they can't write a document, search in browser or write an email properly. More information: lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Nov 11 14:39:13 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391521/+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 1104632] Re: Application spread view (Compiz scale) doesn't work properly after using "Show Desktop"
** Changed in: unity (Ubuntu) Importance: Undecided => High -- 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/1104632 Title: Application spread view (Compiz scale) doesn't work properly after using "Show Desktop" Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: What steps will reproduce the problem? 1. Open two or more windows of an application like Nautilus so that all are visible on the screen 2. Use the "Show Desktop" button to hide the windows 3. Activate the window spread by clicking at the icon of the application you launched two times What is the expected output? - all windows of the application (from current workspace) are shown in the spread, represented by a thumbnail What do you see instead? - all windows are technically "shown" but only the window activated by the first click at the icon has a working thumbnail - the area where the other window-thumbnails should be located is functional but the thumbnails are missing ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.01.21-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.19 Thu Nov 8 00:52:03 PST 2012 GCC version: gcc-Version 4.7.2 (Ubuntu/Linaro 4.7.2-19ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Fri Jan 25 02:19:52 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: nvidia-310, 310.19, 3.8.0-1-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8390] InstallationDate: Installed on 2013-01-22 (2 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130122) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-1-generic root=UUID=db108b5c-1f1d-4fe4-99bd-234f619ae6cf ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: P67 Extreme4 Gen3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd05/11/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnP67Extreme4Gen3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.9~daily13.01.21-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.1-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.1-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.1.901-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu1 xserver.bootTime: Thu Jan 24 15:13:16 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.1.901-0ubuntu2 To manag
[Touch-packages] [Bug 1171435] Re: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1171435 Title: [AV200 - Xonar STX, recording] Microphone is not working on frontpanel Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Microphone is not working on frontpanel of my soundcard Asus Xonar Essence STX. In windows it works normally. Ubuntu 13.04 x64 Tested on the latest kernel 3.9-rc8 With 3.8.0 kernel problem is the same. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 Uname: Linux 3.9.0-030900rc8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simplehuman 2394 F pulseaudio /dev/snd/pcmC0D0c: simplehuman 2394 F...m pulseaudio /dev/snd/controlC1: simplehuman 2394 F pulseaudio Date: Mon Apr 22 15:06:32 2013 InstallationDate: Installed on 2013-02-14 (67 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:STX failed Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_Type: None of the above Title: [AV200 - Xonar STX, recording] Recording problem UpgradeStatus: Upgraded to raring on 2013-02-14 (67 days ago) dmi.bios.date: 08/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 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.:bvr1402:bd08/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1171435/+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 1364911] Re: Support globbing in seat config sections
** Changed in: lightdm Status: Fix Committed => Fix Released -- 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/1364911 Title: Support globbing in seat config sections Status in Light Display Manager: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Bug description: Add support for simple globbing in seat config sections. Example: if a config section [Seat:seatFoo*] is available in lightdm.conf, it will match any seat name starting with "seatFoo", like "seatFooBar", "seatFooBaz", etc. In particular, [Seat:seat*] will match any seat added from logind (including seat0), and [Seat:*] will match any seat (including those eventually added from other mechanisms than logind), just as [SeatDefaults] currently does. It was already merged into trunk in revision 2040, but has been reverted in revision 2042 due to some unexpected problem, so I'm opnening this bug report to keep track of changes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1364911/+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 1366709] Re: please enable opencl
** Changed in: mesa (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1366709 Title: please enable opencl Status in “mesa” package in Ubuntu: Confirmed Bug description: [This is the same as bug #1319835, since I cannot reopen it] Please enable OpenCL in mesa package which is already available in debian package and was disabled in 10.1.0-1ubuntu1. Previuos bug was closed as Won't Fix since there were no software using it: > I don't think there's a point to opencl at the moment, as soon as something in the archive really needs it feel free to reopen it. Here is a list of Ubuntu source package using it (the list may be incomplete): bfgminer clinfo erlang-cl libreoffice-calc pyopencl pyrit-opencl pyviennacl starpu starpu-contrib wine1.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1366709/+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 1190344] Re: lightdm is leaking FDs -fix
** Changed in: lightdm/1.2
Status: Triaged => Fix Released
** Changed in: lightdm/1.12
Status: Triaged => Fix Released
** Changed in: lightdm/1.10
Status: Triaged => Fix Released
** Changed in: lightdm
Status: Triaged => Fix Released
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Released
Status in Light Display Manager 1.12 series:
Fix Released
Status in Light Display Manager 1.2 series:
Fix Released
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
Description of problem:
Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Tested on:
Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
Steps to Reproduce:
1. login on a console and find the pid of main lightdm process then:
# lsof -p {lightdm_pid} |grep FIFO |wc -l
26
2. switch to X console and login through lightdm and then logout
3. go back on comsole
# lsof -p {lightdm_pid} |grep FIFO |wc -l
32
Here is a patch that fixes the issue. It may have several lines offset
because we use modified lightdm but it is good for the original
version too.
regards,
Rumen
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 678421] Re: Error message for a faulty ~/.profile script
** Changed in: lightdm
Status: Fix Committed => Fix Released
--
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/678421
Title:
Error message for a faulty ~/.profile script
Status in GDM: The Gnome Display Manager:
New
Status in Light Display Manager:
Fix Released
Status in Light Display Manager 1.10 series:
Fix Committed
Status in Light Display Manager 1.12 series:
Fix Committed
Status in “gdm” package in Ubuntu:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Status in “gdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Trusty:
In Progress
Status in “gdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Utopic:
In Progress
Bug description:
trusty and utopic SRU requests
==
[Impact]
In case of a syntax error in either of ~/.profile or a few other
similar files, the Xorg login is interrupted, and the user is taken
back to the login screen without an explanation. Debugging this
problem may be a time consuming exercise, especially for non-
experienced users.
With the proposed change, lightdm/gdm does not try to load such a
file, but shows a warning dialog instead. (A warning dialog is also
shown in case of some other type of error, which would not have caused
the login to fail.)
[Test Case]
To reproduce:
* Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
* Log out and find that you can't log in to a graphical session.
After installing the proposed lightdm/gdm version, you'll instead see
the dialog and can log in.
[Regression Potential]
Since this is only about improved exception handling, it does not at
all affect users with correct configuration files. The regression risk
ought to be minimal.
[Original description]
Binary package hint: gdm
After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
made the Xorg startup fail. (At that moment I had already forgotten
the changes made to the .profile). As I had autologin that meant it
kept trying to login and finally showed me the graphics
reconfiguration screen. That sent me to a huge hunt for xorg conf and
setup problems.
Anyway finally tracked this down. I had used bash syntax in .profile
file whereas it was run with sh.
This is not a bug per se but I think a user mistake in ".profile"
shouldn't bring the whole xorg startup to a halt as it does with
autologin. I propose running user ".profile" and ".xprofile" scripts
so that Xsession script continues running even if they have errors.
I'm not sure whether this change would have some negative effects as
well.
1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct
16 19:48:22 UTC 2010 i686 GNU/Linux
2) gdm 2.30.2.is.2.30.0-0ubuntu4
To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/678421/+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 1376357] Re: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log
** Changed in: lightdm Status: Fix Committed => Fix Released -- 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/1376357 Title: lightdm writing the same DEBUG message to /var/log/lightdm/lightdm.log Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Won't Fix Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Bug description: I was trying to figure out where excessive file system writes were coming from on the ubuntu phone (to try to reduce flash writes and hence reduce power consumption) and I spotted that /var/log/lightdm/lightdm.log is getting the same debug message written to every every 300 seconds: tail -f /var/log/lightdm/lightdm.log [+5109.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+5409.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+5709.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+6009.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+6309.64s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+6609.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+6909.67s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+7209.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+7509.66s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+7809.57s] DEBUG: User /org/freedesktop/Accounts/User32011 changed [+8109.65s] DEBUG: User /org/freedesktop/Accounts/User32011 changed while this isn't much of a message, it still is causing file system writes every 5 minutes for the same debug message. Is this necessary? The fact that it is the same message about the same account and that it occurs every 300 seconds make me wonder if we can cull this particular piece of repeated logging. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1376357/+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 1383321] Re: Support XDG DesktopNames field in session files
** Changed in: lightdm Status: Fix Committed => Fix Released ** Changed in: lightdm/1.12 Status: Fix Committed => Fix Released ** Changed in: lightdm/1.10 Status: Fix Committed => Fix Released -- 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/1383321 Title: Support XDG DesktopNames field in session files Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Trusty: Fix Committed Status in “lightdm” source package in Utopic: Fix Committed Status in “lightdm” source package in Vivid: Fix Committed Bug description: [Impact] LightDM doesn't support the XDG standard "DesktopNames" field in session .desktop files. Instead we only support X-LightDM-DesktopName which was used before the standard was set. Newer sessions might expect DesktopNames to work. [Test Case] 1. Install a session which has DesktopNames set in /usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity; 2. Start this session Expected result: XDG_CURRENT_DESKTOP is set to GNOME:Unity Observed result: XDG_CURRENT_DESKTOP is not set [Regression Potential] Low. This feature is only activated if the field is set. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1383321/+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 1377373] Re: Variables defined twice in config files lead to crash
** Changed in: lightdm Status: Fix Committed => Fix Released -- 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/1377373 Title: Variables defined twice in config files lead to crash Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: In Progress Status in “lightdm” source package in Utopic: Fix Released Status in “lightdm” package in Debian: Fix Released Bug description: [Impact] Having the same configuration variable defined in two places causes LightDM to a double free and potentially crash. [Test Case] 1. Install two configuration files in /etc/lightdm/lightdm.conf.d which both define the same variable. 2. Run LightDM Expected result: LightDM runs correctly. Observed result: LightDM double frees a variable (seen with valgrind) and can crash. [Regression Potential] Low. The fix is not to double free the variable. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1377373/+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 1390808] Re: VNC / XDMCP server cannot be configured to listen on specific interfaces
** Changed in: lightdm/1.10 Status: Triaged => Fix Released ** Changed in: lightdm/1.2 Status: Triaged => Fix Released ** Changed in: lightdm/1.12 Status: Triaged => Fix Released ** Changed in: lightdm Status: Triaged => Fix Released -- 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/1390808 Title: VNC / XDMCP server cannot be configured to listen on specific interfaces Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in Light Display Manager 1.12 series: Fix Released Status in Light Display Manager 1.2 series: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “lightdm” source package in Precise: Triaged Status in “lightdm” source package in Trusty: Triaged Status in “lightdm” source package in Utopic: Triaged Status in “lightdm” source package in Vivid: Triaged Bug description: There doesn't seem to be any obvious way to force LightDM's VNC server to listen on only specified interfaces, most notably localhost. This creates a security issue, as the best and most secure way to access a VNC server is through an SSH tunnel where the client will only connect to its localhost on a particular port having all connections through the tunnel to the server's localhost port. If there is a proper way to do this or some sort of work-around, I would be very interested in how to do so. As of right now, this makes LightDM's VNC server unusable for me. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1390808/+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 1392065] Re: grub
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1392065 Title: grub Status in “xorg” package in Ubuntu: Invalid Bug description: grub error and I cannot log without the live CD. Trying ot repair through the live CD. Help me! Please ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 12 21:26:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7592] LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: MSI MS-7592 ProcEnviron: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V26.6 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G41M-S01 (MS-7592) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV26.6:bd03/02/2011:svnMSI:pnMS-7592:pvr5.0:rvnMSI:rnG41M-S01(MS-7592):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7592 dmi.product.version: 5.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Nov 12 21:03:22 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5906 vendor AOC xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1392065/+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 1223699] Re: klipper hangs after launch in Unity
** Changed in: unity (Ubuntu) Importance: Undecided => High -- 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/1223699 Title: klipper hangs after launch in Unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Still actual for Ubuntu 14.10 x64 klipper hangs after launch in Unity. I am getting this output in terminal: klipper QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. klipper(20151) Klipper::loadHistory: Failed to load history resource. Clipboard history cannot be read. : History file does not exist ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: klipper 4:4.11.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-6.12-generic 3.11.0 Uname: Linux 3.11.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 10:31:02 2013 InstallationDate: Installed on 2013-07-31 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True SourcePackage: kde-workspace UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1223699/+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 1390557] Re: [oobe] passcode screen continues after 3 visible dots to confirmation screen
This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20141112.1-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20141112.1-0ubuntu1) vivid; urgency=low [ Sebastien Bacher ] * Update the translations template during the build (LP: #1389786) [ jonas-drange ] * [cellular][phone] titles now using SettingsItemTitle (LP: #1389767) * [wifi] fix multiple issues in the "Connect to other network" dialog (LP: #1387656) [ Andrea Cimitan ] * Delay password set/confirm screens after entering the 4th digit, fixing 1390557 (LP: #1390557) [ CI bot ] * Resync trunk [ Ken VanDine ] * Specify DaemonVersion for upower to support upower 0.99 on vivid (LP: #1390629) * [battery] don't control wifi state with libnm, use the QDBusActionGroup from indicator-network (LP: #1391940) [ Christian Dywan ] * Remove the dialog internals resizing hack (LP: #1376763) -- Ubuntu daily releaseWed, 12 Nov 2014 19:27:21 + ** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1390557 Title: [oobe] passcode screen continues after 3 visible dots to confirmation screen Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Bug description: krillin build 143 Steps to reproduce in the initial set up wizard 1. after selecting your language and setting up wifi continue to the passcode set up screen 2. type in your 4 digit passcode and pay attention to the dots representing the digits Expected result: all 4 dots are visible before screen moves on to confirm your passcode Actual result: only 3 dots are visible and it looks like you only picked a 3 digit passcode It would be great to have a slight delay and show user the last dot before screen moves on to the next step as we currently have when unlocking your device after swiping away the greeter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1390557/+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 1376763] Re: Dialog doesn't take the contents size into consideration
This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20141112.1-0ubuntu1 --- ubuntu-system-settings (0.3+15.04.20141112.1-0ubuntu1) vivid; urgency=low [ Sebastien Bacher ] * Update the translations template during the build (LP: #1389786) [ jonas-drange ] * [cellular][phone] titles now using SettingsItemTitle (LP: #1389767) * [wifi] fix multiple issues in the "Connect to other network" dialog (LP: #1387656) [ Andrea Cimitan ] * Delay password set/confirm screens after entering the 4th digit, fixing 1390557 (LP: #1390557) [ CI bot ] * Resync trunk [ Ken VanDine ] * Specify DaemonVersion for upower to support upower 0.99 on vivid (LP: #1390629) * [battery] don't control wifi state with libnm, use the QDBusActionGroup from indicator-network (LP: #1391940) [ Christian Dywan ] * Remove the dialog internals resizing hack (LP: #1376763) -- Ubuntu daily releaseWed, 12 Nov 2014 19:27:21 + ** Changed in: ubuntu-system-settings (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1376763 Title: Dialog doesn't take the contents size into consideration Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: A dialog doesn't scroll if the text (as in the code example) or its contents exceeds the viewport size. This can be reproduced in e.g. ubuntu-system-settings: (Make sure you're running the very latest from proposed or a USS from October 2014 – debs[1]). 1. Open Ubuntu System Settings 2. Go to the Wi-Fi panel 3. Click "Connect to hidden network…" 4. Choose any security scheme other that "None" 4. Resize the viewport/use landscape on a device What I expect to happen: I can scroll inside the Dialog to access all fields and buttons What happened instead: The content not visible becomes inaccessible Example code: http://paste.ubuntu.com/8479468/ [1] https://launchpad.net/ubuntu-system-settings/+packages UX Solution: Make sure content can scroll vertically if exceeding the maximum height of the dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1376763/+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 1309942] Re: Window Controls not functioning.
Unfortunatly I really miss this feature. The best is: if buttons position is not customiszble anymore please remove the layout option in Ubuntu Tweak asap. -- 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/1309942 Title: Window Controls not functioning. Status in Unity: Won't Fix Status in Unity Tweak Tool: Won't Fix Status in “unity” package in Ubuntu: Won't Fix Bug description: As mentioned earlier the two key functions of Unity Tweak Tool are not working . 1.Windows Control/ Allignment from left to right . 2.Show menu button. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1309942/+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 1392082] Re: call hangup tones should not come out of speaker
** Branch linked: lp:~bfiller/telepathy-ofono/fix-beep-timing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1392082 Title: call hangup tones should not come out of speaker Status in Telephony Service: In Progress Status in “telephony-service” package in Ubuntu: In Progress Status in “telephony-service” package in Ubuntu RTM: New Bug description: call hangup tones currently always are played through the speaker, which is not correct. They should be played through whatever the active audio device is (earpiece, bt headphone, or speaker). To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1392082/+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 1332848] Re: upowerd crashed with SIGABRT in __assert_fail_base()
** Changed in: libimobiledevice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1332848 Title: upowerd crashed with SIGABRT in __assert_fail_base() Status in “libimobiledevice” package in Ubuntu: Confirmed Status in “upower” package in Ubuntu: Confirmed Bug description: error right after login ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.3-0ubuntu2 Architecture: i386 Date: Wed Jun 18 18:21:27 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-05-21 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: Signal: 6 SourcePackage: upower StacktraceTop: __assert_fail_base (fmt=0xb73bab94 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xb740baa1 "data", file=file@entry=0xb740bac9 "plist.c", line=line@entry=194, function=function@entry=0xb740bdcb "plist_copy_node") at assert.c:92 __GI___assert_fail (assertion=0xb740baa1 "data", file=0xb740bac9 "plist.c", line=194, function=0xb740bdcb "plist_copy_node") at assert.c:101 ?? () from /usr/lib/i386-linux-gnu/libplist.so.2 plist_copy () from /usr/lib/i386-linux-gnu/libplist.so.2 ?? () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 Title: upowerd crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1332848/+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 1369216] Re: gpu-manager: /etc/modprobe.d is not a file
** Changed in: upstart (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1369216 Title: gpu-manager: /etc/modprobe.d is not a file Status in “upstart” package in Ubuntu: Confirmed Bug description: Get these lines logged into gpu-manager.log, on that fresh stock installation /etc/modprobe.d is not a file update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: upstart 1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Sep 14 08:42:45 2014 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-14-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) modified.conffile..etc.default.whoopsie: [modified] modified.conffile..etc.gdm.Init.Default: [modified] mtime.conffile..etc.default.whoopsie: 2014-08-29T19:12:47.435075 mtime.conffile..etc.gdm.Init.Default: 2014-09-07T17:01:23.246055 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1369216/+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 1392083] [NEW] Black screen after boot screen - fglrx new installed and fixed
Public bug reported: black screen problem. fglrx (proprietär) new installed and fixed. But very long booting time now. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 12 23:05:46 2014 DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: alsa-hda, 0.201303211238~precise1, 3.2.0-70-generic, x86_64: installed alsa-hda, 0.201303211238~precise1, 3.2.0-72-generic, x86_64: installed fglrx, 13.350.1, 3.13.0-40-generic, x86_64: installed vboxhost, 4.2.26, 3.13.0-40-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e214] InstallationDate: Installed on 2012-05-28 (898 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=00b01f55-6329-416f-a706-a487895773ab ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-11 (1 days ago) dmi.bios.date: 10/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: 990FX Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/12/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Nov 12 21:26:03 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.2 xserver.video_driver: fglrx ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1392083 Title: Black screen after boot screen - fglrx new installed and fixed Status in “xorg” package in Ubuntu: New Bug description: black screen problem. fglrx (proprietär) new installed and fixed. But very long booting time now. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.68-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 12 23:05:46 2014 DistUpgraded: 2014-11-11 21:54:08,837 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: u
[Touch-packages] [Bug 1364911] Re: Support globbing in seat config sections
** Changed in: lightdm Status: Triaged => Fix Committed ** Changed in: lightdm Milestone: None => 1.13.0 ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Importance: Undecided => Wishlist ** Changed in: lightdm (Ubuntu) Status: New => Fix Committed -- 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/1364911 Title: Support globbing in seat config sections Status in Light Display Manager: Fix Committed Status in “lightdm” package in Ubuntu: Fix Committed Bug description: Add support for simple globbing in seat config sections. Example: if a config section [Seat:seatFoo*] is available in lightdm.conf, it will match any seat name starting with "seatFoo", like "seatFooBar", "seatFooBaz", etc. In particular, [Seat:seat*] will match any seat added from logind (including seat0), and [Seat:*] will match any seat (including those eventually added from other mechanisms than logind), just as [SeatDefaults] currently does. It was already merged into trunk in revision 2040, but has been reverted in revision 2042 due to some unexpected problem, so I'm opnening this bug report to keep track of changes. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1364911/+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 1377332] Re: [TOPBLOCKER] UI randomly freezes
** Changed in: unity8 (Ubuntu) Importance: High => Critical ** Changed in: ubuntu-app-launch (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377332 Title: [TOPBLOCKER] UI randomly freezes Status in “cgmanager” package in Ubuntu: Incomplete Status in “ubuntu-app-launch” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Status in “ubuntu-app-launch” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: In Progress Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1377332/+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 1392082] [NEW] call hangup tones should not come out of speaker
Public bug reported: call hangup tones currently always are played through the speaker, which is not correct. They should be played through whatever the active audio device is (earpiece, bt headphone, or speaker). ** Affects: telephony-service Importance: High Assignee: Tiago Salem Herrmann (tiagosh) Status: In Progress ** Affects: telephony-service (Ubuntu) Importance: High Assignee: Tiago Salem Herrmann (tiagosh) Status: In Progress ** Affects: telephony-service (Ubuntu RTM) Importance: High Assignee: Tiago Salem Herrmann (tiagosh) Status: New ** Tags: rtm14 ** Also affects: telephony-service (Ubuntu) Importance: Undecided Status: New ** Also affects: telephony-service (Ubuntu RTM) Importance: Undecided Status: New ** Tags added: rtm14 ** Changed in: telephony-service Importance: Undecided => High ** Changed in: telephony-service (Ubuntu) Importance: Undecided => High ** Changed in: telephony-service (Ubuntu RTM) Importance: Undecided => High ** Changed in: telephony-service Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) ** Changed in: telephony-service (Ubuntu RTM) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) ** Changed in: telephony-service (Ubuntu) Status: New => In Progress ** Changed in: telephony-service Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1392082 Title: call hangup tones should not come out of speaker Status in Telephony Service: In Progress Status in “telephony-service” package in Ubuntu: In Progress Status in “telephony-service” package in Ubuntu RTM: New Bug description: call hangup tones currently always are played through the speaker, which is not correct. They should be played through whatever the active audio device is (earpiece, bt headphone, or speaker). To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1392082/+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)
This has been fixed upstream: https://github.com/karelzak/util-linux/issues/119 https://github.com/karelzak/util-linux/commit/98b539c25caede8534ffaf06e67a694eeb3bc6cb ** Package changed: gvfs (Ubuntu) => util-linux (Ubuntu) -- 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: Confirmed 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 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 1390961] Re: bug at initializing a radeon graphics card on pci-e
Ok, So I fiddled with kernel boot parameters and enable_mtrr_cleanup seems to do fix the MTRR mess like in: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=35910738-c8fc-48e5-8b80-5c7766a720fc ro enable_mtrr_cleanup So I'll close the bug ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1390961 Title: bug at initializing a radeon graphics card on pci-e Status in “xorg” package in Ubuntu: Invalid Bug description: I have a Thinkpad T60 running 14.10 with a built-in intel graphics card. I plug the laptop in a docking station which has a radeon cedar graphics card on a pci-e port. Card can't be initialized. Nov 9 19:35:04 pico-T60 kernel: [ 133.635825] [drm] radeon kernel modesetting enabled. Nov 9 19:35:04 pico-T60 kernel: [ 133.656080] radeon :0c:00.0: Refused to change power state, currently in D3 Nov 9 19:35:04 pico-T60 kernel: [ 133.656672] [drm] initializing kernel modesetting (CEDAR 0x1002:0x68F9 0x1043:0x0471). Nov 9 19:35:04 pico-T60 kernel: [ 133.656703] [drm] register mmio base: 0x8800 Nov 9 19:35:04 pico-T60 kernel: [ 133.656707] [drm] register mmio size: 131072 Nov 9 19:35:04 pico-T60 kernel: [ 133.656769] radeon :0c:00.0: Invalid ROM contents Nov 9 19:35:04 pico-T60 kernel: [ 133.656903] radeon :0c:00.0: Invalid ROM contents Nov 9 19:35:04 pico-T60 kernel: [ 133.656997] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM Nov 9 19:35:04 pico-T60 kernel: [ 133.657106] radeon :0c:00.0: Fatal error during GPU init Nov 9 19:35:04 pico-T60 kernel: [ 133.657204] [drm] radeon: finishing device. Nov 9 19:35:04 pico-T60 kernel: [ 133.657208] [TTM] Memory type 2 has not been initialized Nov 9 19:35:04 pico-T60 kernel: [ 133.664743] radeon: probe of :0c:00.0 failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 Uname: Linux 3.18.0-031800rc2-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Nov 9 20:03:03 2014 DistUpgraded: 2014-10-30 20:59:07,260 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.18, 3.16.0-24-generic, i686: installed virtualbox, 4.3.18, 3.18.0-031800rc2-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] Subsystem: Lenovo ThinkPad R60/T60/X60 series [17aa:201a] InstallationDate: Installed on 2012-06-18 (874 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) MachineType: LENOVO 1952AT7 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-031800rc2-generic root=UUID=35910738-c8fc-48e5-8b80-5c7766a720fc ro quiet splash enable_mtrr_cleanup pciehp.pciehp_force=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-30 (9 days ago) dmi.bios.date: 03/21/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE7WW (2.27 ) dmi.board.name: 1952AT7 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: 1952at7l3a9167 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE7WW(2.27):bd03/21/2011:svnLENOVO:pn1952AT7:pvrThinkPadT60:rvnLENOVO:rn1952AT7:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 1952AT7 dmi.product.version: ThinkPad T60 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Nov 9 19:58:46 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logf
[Touch-packages] [Bug 1388235] Re: Battery icon turns red at 30%
@charles can you check, seems its not doing it per spec or maybe theme is wrong ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+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] [NEW] Does not detect hotplugged storage device (exfat)
You have been subscribed to a public bug: 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 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) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug utopic -- Does not detect hotplugged storage device (exfat) https://bugs.launchpad.net/bugs/1389021 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. -- 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 1387708] Re: [TOPBLOCKER] Location services not getting location
** Changed in: location-service (Ubuntu-rtm 14.09) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387708 Title: [TOPBLOCKER] Location services not getting location Status in Location Service: New Status in “location-service” package in Ubuntu: In Progress Status in “location-service” package in Ubuntu RTM: Fix Released Status in “location-service” source package in 14.09: Fix Released Bug description: Failing to get location fix from application. Neither network based nor gps location works. Bug has now been seen on 3 phones with and without SIM installed. HERE service seems to be running, but no reasonable location is reported. GPS is failing to get fix, tested with phone placed for 2 hours outside. On two of those phones location was working fine, but with OTA update to ~135 stopped working. hard to guess working image but somewhere around 129~131 Problem is now reproducible on RTM release 137 To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1387708/+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 1190344] Re: lightdm is leaking FDs -fix
** Branch linked: lp:lightdm/1.2
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Triaged
Status in Light Display Manager 1.10 series:
Triaged
Status in Light Display Manager 1.12 series:
Triaged
Status in Light Display Manager 1.2 series:
Triaged
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
Description of problem:
Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Tested on:
Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
Steps to Reproduce:
1. login on a console and find the pid of main lightdm process then:
# lsof -p {lightdm_pid} |grep FIFO |wc -l
26
2. switch to X console and login through lightdm and then logout
3. go back on comsole
# lsof -p {lightdm_pid} |grep FIFO |wc -l
32
Here is a patch that fixes the issue. It may have several lines offset
because we use modified lightdm but it is good for the original
version too.
regards,
Rumen
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1351528] Re: boot fails for LVM on degraded raid due to missing device tables at premount
See https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1077650 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1351528 Title: boot fails for LVM on degraded raid due to missing device tables at premount Status in “lvm2” package in Ubuntu: Confirmed Bug description: This is a Trusty installation with combined root + /boot within LVM on top of mdraid (type 1.x) RAID1. Raid1 was built with one missing disk (degraded). [method: basically create raid/VG/LV setup in shell first then point installer at the lvm. At the end of the install create a chroot, add the mdadm pkg, and update-initramfs before reboot.] The boot process fails with the following messages: Incrementally starting RAID arrays... mdadm: CREATE user root not found mdadm: CREATE group disk not found Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continued visibility of text boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d (instead of the expected -wi-a) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+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 1383321] Re: Support XDG DesktopNames field in session files
** Changed in: lightdm (Ubuntu Trusty) Status: New => Triaged ** Also affects: lightdm/1.12 Importance: Undecided Status: New ** Changed in: lightdm Status: Fix Released => Fix Committed ** Changed in: lightdm/1.12 Status: New => Fix Committed ** Changed in: lightdm/1.12 Milestone: None => 1.12.2 ** Changed in: lightdm Milestone: None => 1.13.0 ** Changed in: lightdm/1.12 Importance: Undecided => Medium ** Changed in: lightdm (Ubuntu Utopic) Status: Fix Released => Fix Committed ** Changed in: lightdm (Ubuntu Trusty) Status: Triaged => Fix Committed ** Also affects: lightdm (Ubuntu Vivid) Importance: Medium Status: Fix Released ** Changed in: lightdm (Ubuntu Vivid) Status: Fix Released => Fix Committed -- 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/1383321 Title: Support XDG DesktopNames field in session files Status in Light Display Manager: Fix Committed Status in Light Display Manager 1.10 series: Fix Committed Status in Light Display Manager 1.12 series: Fix Committed Status in “lightdm” package in Ubuntu: Fix Committed Status in “lightdm” source package in Trusty: Fix Committed Status in “lightdm” source package in Utopic: Fix Committed Status in “lightdm” source package in Vivid: Fix Committed Bug description: [Impact] LightDM doesn't support the XDG standard "DesktopNames" field in session .desktop files. Instead we only support X-LightDM-DesktopName which was used before the standard was set. Newer sessions might expect DesktopNames to work. [Test Case] 1. Install a session which has DesktopNames set in /usr/share/xsessions/name.desktop. i.e. DesktopNames=GNOME;Unity; 2. Start this session Expected result: XDG_CURRENT_DESKTOP is set to GNOME:Unity Observed result: XDG_CURRENT_DESKTOP is not set [Regression Potential] Low. This feature is only activated if the field is set. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1383321/+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 1392064] Re: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf
Here is a video of the bug, LightDM ignores the settings and moves the pointer to the right https://drive.google.com/file/d/0B4c5GbInagPqZEZvUlQxZ01qX0U/view?usp=sharing Here is a video of a working user session after logging in from LightDM, proving that the script works. https://drive.google.com/file/d/0B4c5GbInagPqNW5BU1BsWGV2cDA/view?usp=sharing -- 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/1392064 Title: lightdm ignores .conf file in /usr/share/lightdm/lightdm.conf Status in “lightdm” package in Ubuntu: New Bug description: Setup: Ubuntu 14.04.1LTS IIyama 19" Pro-Lite Touchscreen Dell 17" regular monitor Due to another bug in the detection of input devices I had to write a script to tell Ubuntu which screen to use the touch from the touchscreen. so I put the following two entries into a basic bash script based on xinput list and xrandr -q #!/bin/bash xinput map-to-output 12 DVI-I-1 xrandr --output DVI-I-1 --primary = I added this script to /usr/share/lightdm/lightdm.conf.d/50-dualscreen-touch.conf and the contents look like this. [SeatDefaults] greeter-setup-script=/usr/local/bin/iiyama-touchscreen.sh session-setup-script=/usr/local/bin/iiyama-touchscreen.sh When I start a user session the touchscreen is calibrated and works normally with the touch happening on the touchscreen. As soon as I logoff into LightDM the touch calibration is off moving the pointer a logarithmic distance from the left of the touchscreen. As soon as I log in again, no problems, touch works great, log back out into the lightDM greeter and boom touch is all crazy. Can lightdm please detect that a touchscreen can only accept touch input and output to the touchscreen device?? Or at least have lightdm actually run the script when given? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 12 22:11:38 2014 InstallationDate: Installed on 2014-11-03 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) LightdmConfig: [SeatDefaults] autologin-user=boerske SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1392064/+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 1190344] Re: lightdm is leaking FDs -fix
** Branch linked: lp:lightdm/1.12
** Branch linked: lp:lightdm/1.10
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Triaged
Status in Light Display Manager 1.10 series:
Triaged
Status in Light Display Manager 1.12 series:
Triaged
Status in Light Display Manager 1.2 series:
Triaged
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
Description of problem:
Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Tested on:
Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
Steps to Reproduce:
1. login on a console and find the pid of main lightdm process then:
# lsof -p {lightdm_pid} |grep FIFO |wc -l
26
2. switch to X console and login through lightdm and then logout
3. go back on comsole
# lsof -p {lightdm_pid} |grep FIFO |wc -l
32
Here is a patch that fixes the issue. It may have several lines offset
because we use modified lightdm but it is good for the original
version too.
regards,
Rumen
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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 1351528] Re: boot fails for LVM on degraded raid due to missing device tables at premount
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1351528 Title: boot fails for LVM on degraded raid due to missing device tables at premount Status in “lvm2” package in Ubuntu: Confirmed Bug description: This is a Trusty installation with combined root + /boot within LVM on top of mdraid (type 1.x) RAID1. Raid1 was built with one missing disk (degraded). [method: basically create raid/VG/LV setup in shell first then point installer at the lvm. At the end of the install create a chroot, add the mdadm pkg, and update-initramfs before reboot.] The boot process fails with the following messages: Incrementally starting RAID arrays... mdadm: CREATE user root not found mdadm: CREATE group disk not found Incrementally starting RAID arrays... and slowly repeats the above at this point. workaround: - add break=premount to grub kernel line entry - for continued visibility of text boot output also remove quiet, splash and possibly set gxmode 640x480 now @ initramfs prompt: mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok lvm lvs output attributes are as follows: -wi-d (instead of the expected -wi-a) lvs manpage this means device tables are missing (device mapper?) FIX: simply run lvm vgchange -ay and exit initramsfs. This will lead to a booting system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+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 1391944] Re: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127
*** This bug is a duplicate of bug 1390825 *** https://bugs.launchpad.net/bugs/1390825 ** This bug has been marked a duplicate of bug 1390825 package linux-image-3.16.0-24-generic 3.16.0-24.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1391944 Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 Status in “initramfs-tools” package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-25-generic 3.16.0-25.33 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: francesco 1932 F pulseaudio /dev/snd/controlC0: francesco 1932 F pulseaudio Date: Wed Nov 12 11:06:00 2014 DuplicateSignature: package:linux-image-3.16.0-25-generic:3.16.0-25.33:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=640ae5a1-e82e-415e-a444-9f08d1fd6830 InstallationDate: Installed on 2014-10-28 (14 days ago) InstallationMedia: Xubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Dell Inc. Precision M4800 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=9079ba0d-4359-445c-bb13-78b03e96486a ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-15 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-25-generic 3.16.0-25.33 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 077KCT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/18/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1391944/+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 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run
** Changed in: whoopsie (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1389357 Title: whoopsie reuses CRASH_DB_IDENTIFIER on next run Status in “whoopsie” package in Ubuntu: Confirmed Bug description: On Vivid, Ubuntu 15.04, I observed the following behavior. bdmurray@blacklightning:~/Downloads$ sudo stop whoopsie [sudo] password for bdmurray: whoopsie stop/waiting bdmurray@blacklightning:~/Downloads$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com CRASH_DB_IDENTIFIER=deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd APPORT_REPORT_DIR=/var/crash/ whoopsie -f [11:07:17] Using lock path: /var/crash/whoopsie_lock [11:07:18] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] online bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd bdmurray@blacklightning:~/Downloads$ sudo start whoopsie whoopsie start/running, process 9083 bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd Notice, how the same CRASH_DB_IDENTIFIER was used by whoopsie when starting up, rather than calculating the system identifier. This may lead to crashes being reported under the wrong system-identifier if people switch from setting the environmental variable to just running whoopsie. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1389357/+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 1381583] Re: imported pictures should show in Event for today
** Also affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Also affects: gallery-app (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: gallery-app (Ubuntu) Status: New => In Progress ** Changed in: gallery-app (Ubuntu) Importance: Undecided => High ** Changed in: gallery-app (Ubuntu RTM) Status: New => In Progress ** Changed in: gallery-app (Ubuntu RTM) Importance: Undecided => High ** Changed in: gallery-app (Ubuntu) Assignee: (unassigned) => Arthur Mello (artmello) ** Changed in: gallery-app (Ubuntu RTM) Assignee: (unassigned) => Arthur Mello (artmello) ** Tags added: ota-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1381583 Title: imported pictures should show in Event for today Status in Gallery App: In Progress Status in Ubuntu UX bugs: New Status in “gallery-app” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: When pictures are imported into the gallery, via content-hub, we should always display them in the Event for the current day. Right now, the picture is played in the Event that corresponds to the metadata creation date which is very confusing because after the picture is imported you can't find it easily. Arthur and I discussed modifiying one of the standard exif tags (like DateTime, but don't modify CreationDate) with the current date of import as the gallery already sorts by a series of tags. Another solution would be to add a custom tag like (importDate) and change the sort to use that if it exists before falling back to other tags. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1381583/+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 1382109] Re: Events view should be shown on import
** Also affects: gallery-app (Ubuntu) Importance: Undecided Status: New ** Also affects: gallery-app (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: gallery-app (Ubuntu) Status: New => In Progress ** Changed in: gallery-app (Ubuntu) Importance: Undecided => High ** Changed in: gallery-app (Ubuntu) Assignee: (unassigned) => Arthur Mello (artmello) ** Changed in: gallery-app (Ubuntu RTM) Importance: Undecided => High ** Changed in: gallery-app (Ubuntu RTM) Status: New => In Progress ** Changed in: gallery-app (Ubuntu RTM) Assignee: (unassigned) => Arthur Mello (artmello) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1382109 Title: Events view should be shown on import Status in Gallery App: In Progress Status in “gallery-app” package in Ubuntu: In Progress Status in “gallery-app” package in Ubuntu RTM: In Progress Bug description: If a photo is imported via the content-hub, we should always make sure to display the Events view as the photo will show up by default there. Currenty if the gallery is open to a specific photo or album, after the import occurs we don't update the view so user has no idea where the imported picture is. Would be nice to directly open the imported picture but this won't work as we might get multiple import events in a row from content-hub in the case where the user "Dimissed" the open dialog multiple times. Next time gallery-app launched or displayed it will be delivered multiple events so we would not know which to open. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1382109/+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 1190344] Re: lightdm is leaking FDs -fix
** Branch linked: lp:lightdm
--
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/1190344
Title:
lightdm is leaking FDs -fix
Status in Light Display Manager:
Triaged
Status in Light Display Manager 1.10 series:
Triaged
Status in Light Display Manager 1.12 series:
Triaged
Status in Light Display Manager 1.2 series:
Triaged
Status in “lightdm” package in Ubuntu:
Triaged
Status in “lightdm” source package in Precise:
Triaged
Status in “lightdm” source package in Trusty:
Triaged
Status in “lightdm” source package in Utopic:
Triaged
Status in “lightdm” source package in Vivid:
Triaged
Status in Fedora:
Unknown
Bug description:
Description of problem:
Each time the greeter starts the number of open FDs increase. After each
login and logout cycle the number of open FDs is increased. Which over time
leads to impossible logins and the message in /var/log/messages is:
Jun 12 02:44:24 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipe to communicate with session process: To...en files
Jun 12 02:45:29 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Jun 12 02:47:47 node3 lightdm[17471]: ** (lightdm:17471): WARNING **: Failed
to create pipes: Too many open files
Tested on:
Fedora 19 and Ubuntu 13.04 - lightdm 1.6.0
Steps to Reproduce:
1. login on a console and find the pid of main lightdm process then:
# lsof -p {lightdm_pid} |grep FIFO |wc -l
26
2. switch to X console and login through lightdm and then logout
3. go back on comsole
# lsof -p {lightdm_pid} |grep FIFO |wc -l
32
Here is a patch that fixes the issue. It may have several lines offset
because we use modified lightdm but it is good for the original
version too.
regards,
Rumen
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1190344/+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
