[Touch-packages] [Bug 1602388] Re: Sudo crashed without I even noticed...
** Description changed: Yes that's all, I just noticed the apport window popping out when I booted. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 12 00:02:24 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-01-07 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: sudo parted /dev/sda SourcePackage: sudo UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago) VisudoCheck: - /etc/sudoers：解析正确 - /etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确 - /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确 - /etc/sudoers.d/README：解析正确 - /etc/sudoers.d/buildd：解析正确 + /etc/sudoers：解析正确(=OK) + /etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确 + /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确 + /etc/sudoers.d/README：解析正确 + /etc/sudoers.d/buildd：解析正确 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1602388 Title: Sudo crashed without I even noticed... Status in sudo package in Ubuntu: New Bug description: Yes that's all, I just noticed the apport window popping out when I booted. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 12 00:02:24 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-01-07 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: sudo parted /dev/sda SourcePackage: sudo UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago) VisudoCheck: /etc/sudoers：解析正确(=OK) /etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确 /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确 /etc/sudoers.d/README：解析正确 /etc/sudoers.d/buildd：解析正确 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1602388/+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 1602388] [NEW] Sudo crashed without I even noticed...
Public bug reported: Yes that's all, I just noticed the apport window popping out when I booted. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 12 00:02:24 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-01-07 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: sudo parted /dev/sda SourcePackage: sudo UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago) VisudoCheck: /etc/sudoers：解析正确 /etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确 /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确 /etc/sudoers.d/README：解析正确 /etc/sudoers.d/buildd：解析正确 ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1602388 Title: Sudo crashed without I even noticed... Status in sudo package in Ubuntu: New Bug description: Yes that's all, I just noticed the apport window popping out when I booted. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 Uname: Linux 4.6.0-pf1-buo-ren-autodetected-optimized x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 12 00:02:24 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2016-01-07 (186 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: sudo parted /dev/sda SourcePackage: sudo UpgradeStatus: Upgraded to xenial on 2016-04-07 (96 days ago) VisudoCheck: /etc/sudoers：解析正确 /etc/sudoers.d/Patch_Launchpad_Bug_1373495_don't_preserve_HOME_environment_variable_by_default：解析正确 /etc/sudoers.d/Preserve_input_method_required_environmental_variables：解析正确 /etc/sudoers.d/README：解析正确 /etc/sudoers.d/buildd：解析正确 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1602388/+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 1600785] [NEW] Possible syntax error in the info doc
Public bug reported: When opening info:sed#Command_and_Option_Index in Yelp the following error appears: `` This page contains the following errors: error on line 1115 at column 44: PCDATA invalid Char value 8 Below is a rendering of the page up to the first error. `` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sed 4.2.2-7 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 11 19:30:00 2016 InstallationDate: Installed on 2016-01-07 (185 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sed UpgradeStatus: Upgraded to xenial on 2016-04-07 (94 days ago) ** Affects: sed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1600785 Title: Possible syntax error in the info doc Status in sed package in Ubuntu: New Bug description: When opening info:sed#Command_and_Option_Index in Yelp the following error appears: `` This page contains the following errors: error on line 1115 at column 44: PCDATA invalid Char value 8 Below is a rendering of the page up to the first error. `` ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sed 4.2.2-7 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 11 19:30:00 2016 InstallationDate: Installed on 2016-01-07 (185 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: sed UpgradeStatus: Upgraded to xenial on 2016-04-07 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1600785/+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 1585863] Re: WiFi malfunction after suspend & resume stress
@fourdollars The xenial debdiff seems to be tainted by color codes...? -- 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/1585863 Title: WiFi malfunction after suspend & resume stress Status in network-manager package in Ubuntu: New Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863/+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 1553211] Re: gnome-software does not treat recommends and suggests as plugins to applications | impossible to install "technical" packages (plugins, kernels...)
** Bug watch added: GNOME Bug Tracker #711638 https://bugzilla.gnome.org/show_bug.cgi?id=711638 ** Also affects: gnome-software via https://bugzilla.gnome.org/show_bug.cgi?id=711638 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1553211 Title: gnome-software does not treat recommends and suggests as plugins to applications | impossible to install "technical" packages (plugins, kernels...) Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 will be useless for "normal" people if they can't find every software package as they did before. To force users to use gnome-software will be a regression! Examples: In old Software Center, you could add gimp plug-ins (plug-ins are recommends and suggests packages of gimp) by going in gimp description and check the plug-ins you want! In old Software Center, you could install another version of linux kernel by typing "linux" then click at bottom left to show the packages. Now, they have to use apt-get or install synaptic! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.91~git20160229.ceb6b9d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 4 15:06:20 2016 InstallationDate: Installed on 2016-01-07 (57 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160105) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1553211/+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 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured
Sorry, please entirely ignore #17 as I wrongly recognize my system as upgraded from trusty, but in fact it is a wily clean install instead. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured Status in apt package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1560797/+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 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured
The system that I've used is based on my os distro project "Taiwan Community Customized Unofficial Ubuntu Operating System" which is based on Ubuntu trusty and is downloadable from https://github.com/Ubuntu- Taiwan-Community/Ubuntu-TW- Ubuntu/releases/tag/v0.3.0-release201510120351 , I've used this system to sequentially upgraded to 15.10 and after that, 16.04. I'm currently trying to repeat the same process on a VM and try to reproduce the same issue. Let's try to fix this bug before the xenial official release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured Status in apt package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1560797/+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 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured
``` (Reading database ... 100%^M(Reading database ... 692766 f iles and directories currently installed.) Preparing to unpack .../libgcrypt20_1.6.5-2_amd64.deb ... De-configuring libgcrypt20:i386 (1.6.3-2ubuntu1.1) ... Unpacking libgcrypt20:amd64 (1.6.5-2) over (1.6.3-2ubuntu1.1) ... Preparing to unpack .../libgcrypt20_1.6.5-2_i386.deb ... Unpacking libgcrypt20:i386 (1.6.5-2) over (1.6.3-2ubuntu1.1) ... (...) Unpacking cgmanager (0.39-2ubuntu5) over (0.39-2ubuntu2) ... Processing triggers for man-db (2.7.4-1) ... dpkg: dependency problems prevent configuration of systemd: systemd depends on libgcrypt20 (>= 1.6.1); however: Package libgcrypt20:amd64 is not configured yet. ``` libgcrypt2 is unpacked by it's newer version, but isn't configured before systemd's configuration That's all I can tell as I'm not familiar with APT. -- 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/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+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 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured
@Martin > Can you please look in /var/log/dist-upgrade/ whether there is a more > complete term log there? Here's your log. ** Attachment added: "/var/log/dist-upgrade/apt-term.log" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+attachment/4628024/+files/apt-term.log ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+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 1560797] Re: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured
> Seems to be resolved by today's update to systemd-sysv 229-3ubuntu1 No, I still encounter this issue on 4/6 and I'm sure all updates are installed. So the bug still exist. -- 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/1560797 Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: libgcrypt20 was unconfigured Status in systemd package in Ubuntu: Confirmed Bug description: Happened during upgrade to 16.04, don't know any more details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 Uname: Linux 4.4.5-040405-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 22 22:56:03 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2013-04-24 (1064 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.7 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-03-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560797/+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 857651]
Hi Matthias (or others), can anyone start reviewing the patch? (puppy- dog eyes) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/857651 Title: Unable to hide users from login screen / user switcher Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Bug description: Users that I have appended to the 'hidden-users' field in /etc/lightdm/users.conf are not actually hidden. They are still listed on the login screen and in Unity's user switching menu. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Fri Sep 23 11:44:29 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago) mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175 To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/857651/+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 1468027] Re: change default CJK fonts to Noto CJK
Using Regular here $ LC_CTYPE=zh_TW.UTF-8 fc-match -a | head -7 SourceHanSansTW-Regular.otf: "思源黑體 TW" "Regular" SourceHanSansCN-Regular.otf: "思源黑体 CN" "Regular" SourceHanSansJP-Regular.otf: "Source Han Sans JP" "Regular" DroidSansFallbackFull.ttf: "Droid Sans Fallback" "Regular" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSans.ttf: "DejaVu Sans" "Book" DejaVuSansCondensed.ttf: "DejaVu Sans" "Condensed" currently no much problem about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1468027 Title: change default CJK fonts to Noto CJK Status in fonts-noto-cjk package in Ubuntu: In Progress Status in language-selector package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: In Progress Bug description: just realize that fonts-noto-cjk is available in the repository, finally its packaged. i don't really know about korean community. But for Chinese and Japanese community, i think that the answer is clear. noto-cjk is definitely better what we had before, like fonts- wqy and fonts-droid. Android community had received these complains for years, finally they got them fixed on lollipop. Fedora also set it as default chinese font start from F21. and of course, i still hope that ubuntu could drop those 69-language-selector fontconfig files, just like what F13 did. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto-cjk/+bug/1468027/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Tags added: wily xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in sudo package in Ubuntu: Confirmed Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may create files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users' account again and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch)(no, Debian is NOT affected by this issue) that makes $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. [RootSudo - Community Help Wiki](https://help.ubuntu.com/community/RootSudo) wrongly tells that graphical application shouldn't be launched by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373495/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users' account again and even make the user failed to login(due to .Xauthority file owner is incorrect) - In my opinion the Ubuntu patch(keep_home_by_default.patch) that make - $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu - should use the safest configuration to general users by default), any - user wish to run command as root using their HOME directory should set - env_keep in /etc/sudoers themselves and acknowledging the consequences. + In my opinion the Ubuntu patch(keep_home_by_default.patch)(no, Debian is + NOT affected by this issue) that makes $HOME variable keep in sudo is + INSANE and should be reverted(Ubuntu should use the safest configuration + to general users by default), any user wish to run command as root using + their HOME directory should set env_keep in /etc/sudoers themselves and + acknowledging the consequences. - RootSudo - Community Help - Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that + [RootSudo - Community Help + Wiki](https://help.ubuntu.com/community/RootSudo) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 ** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users' account again and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch)(no, Debian is NOT affected by this issue) that makes $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. [RootSudo - Community Help Wiki](https://help.ubuntu.com/community/RootSudo) wrongly tells that - graphical application shouldn't be launch by sudo, but in fact the real - issue falls into this bug. + graphical application shouldn't be launched by sudo, but in fact the + real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 ** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by - root may write files (e.g. $HOME/.Xauthority , program config files) + root may create files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users'
[Touch-packages] [Bug 1526968] [NEW] Gstreamer play with no sound when playing video with OPUS audio track
Public bug reported: The same video plays correctly on VLC, though. ## gst-play-1.0 console output ## ``` $ gst-play-1.0 Undertale\ \[Pacifist\ AMV\]\ -\ Glad\ You\ Came-4dTTUDN1lV0.mkv Now playing Undertale [Pacifist AMV] - Glad You Came-4dTTUDN1lV0.mkv Missing plugin: audio/x-unknown decoder WARNING No decoder available for type 'audio/x-unknown, codec-id=(string)A_OPUS'. WARNING debug information: gsturidecodebin.c(930): unknown_type_cb (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0 libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_32 libva info: va_openDriver() returns 0 ``` ## Used 3rd party softwares ## * [Ubuntu Multimedia for Trusty : Doug McMahon](https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 17 05:49:17 2015 InstallationDate: Installed on 2015-10-02 (75 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1526968 Title: Gstreamer play with no sound when playing video with OPUS audio track Status in gstreamer1.0 package in Ubuntu: New Bug description: The same video plays correctly on VLC, though. ## gst-play-1.0 console output ## ``` $ gst-play-1.0 Undertale\ \[Pacifist\ AMV\]\ -\ Glad\ You\ Came-4dTTUDN1lV0.mkv Now playing Undertale [Pacifist AMV] - Glad You Came-4dTTUDN1lV0.mkv Missing plugin: audio/x-unknown decoder WARNING No decoder available for type 'audio/x-unknown, codec-id=(string)A_OPUS'. WARNING debug information: gsturidecodebin.c(930): unknown_type_cb (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0 libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_32 libva info: va_openDriver() returns 0 ``` ## Used 3rd party softwares ## * [Ubuntu Multimedia for Trusty : Doug McMahon](https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 17 05:49:17 2015 InstallationDate: Installed on 2015-10-02 (75 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1526968/+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 1526968] Re: Gstreamer play with no sound when playing video with OPUS audio track
** Attachment added: "Bug reproducing video(from Youtube)" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1526968/+attachment/4535924/+files/Undertale%20%5BPacifist%20AMV%5D%20-%20Glad%20You%20Came-4dTTUDN1lV0.mkv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1526968 Title: Gstreamer play with no sound when playing video with OPUS audio track Status in gstreamer1.0 package in Ubuntu: New Bug description: The same video plays correctly on VLC, though. ## gst-play-1.0 console output ## ``` $ gst-play-1.0 Undertale\ \[Pacifist\ AMV\]\ -\ Glad\ You\ Came-4dTTUDN1lV0.mkv Now playing Undertale [Pacifist AMV] - Glad You Came-4dTTUDN1lV0.mkv Missing plugin: audio/x-unknown decoder WARNING No decoder available for type 'audio/x-unknown, codec-id=(string)A_OPUS'. WARNING debug information: gsturidecodebin.c(930): unknown_type_cb (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0 libva info: VA-API version 0.36.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/i386-linux-gnu/dri/nvidia_drv_video.so libva info: Found init function __vaDriverInit_0_32 libva info: va_openDriver() returns 0 ``` ## Used 3rd party softwares ## * [Ubuntu Multimedia for Trusty : Doug McMahon](https://launchpad.net/~mc3man/+archive/ubuntu/trusty-media) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgstreamer1.0-0 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29 Uname: Linux 3.13.0-71-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 17 05:49:17 2015 InstallationDate: Installed on 2015-10-02 (75 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1526968/+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 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)
Hi, not really relate to the bug but my apport window listed an invalid
duplicate bug #1509643, please checkout the attatched screenshot:
** Attachment added: "Apport screenshot."
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1503979/+attachment/4526905/+files/Ubuntu_022.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1503979
Title:
ubuntu-support-status throws exeption No date tag found (regression)
Status in python-apt package in Ubuntu:
Confirmed
Status in update-manager package in Ubuntu:
Confirmed
Bug description:
Description: Ubuntu 14.04.3 LTS
Release: 14.04
update-manager-core: 1:0.196.14
Since the last update ubuntu-support-status throws
Traceback (most recent call last):
File "/usr/bin/ubuntu-support-status", line 133, in
pkg.name, support_tag)
File "/usr/bin/ubuntu-support-status", line 49, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1503979/+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 1072556] Re: Can not adduser with just number
And while I didn't meant that it's 100% impossible to create such usernames, it is really not a good practice since programs distinguish username from UID by the first character. Therefore I'd like to make this bug `invalid`. ** Changed in: adduser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1072556 Title: Can not adduser with just number Status in adduser package in Ubuntu: Invalid Bug description: Was trying to add a user via adduser with just the username of 1600 and the following is displayed: adduser: Please enter a username matching the regular expression configured via the NAME_REGEX[_SYSTEM] configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. I checked the options fore the NAME_REGEX in /etc/adduser.conf and it is commented out and shouldn't be affecting the adduser command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1072556/+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 760140] Re: HOME environmental variable no long preserved with sudo by default
I personally believe that the decision of adding this patch is wrong, please refer Bug #1373495. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/760140 Title: HOME environmental variable no long preserved with sudo by default Status in sudo package in Ubuntu: Fix Released Status in sudo source package in Natty: Fix Released Bug description: Binary package hint: sudo As discussed on ubuntu-devel in February https://lists.ubuntu.com/archives/ubuntu- devel/2011-February/032490.html: sudo sh -c 'echo $HOME' no longer returns the current users home directory rather it returns /root. This is a change in behavior from Maverick which kept $HOME. The following debian bug contains information about why this is happening now - http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=596847. The HOME and MAIL environment variables are now reset based on the target user's password database entry when the env_reset sudoers option is enabled (which is the case in the default configuration). Something should be done to ensure there isn't a regression and that $HOME is preserved by default. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: sudo 1.7.4p4-5ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-8.41-server 2.6.38.2 Uname: Linux 2.6.38-8-server x86_64 NonfreeKernelModules: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs reiserfs nls_utf8 isofs nfs lockd fscache nfs_acl auth_rpcgss sunrpc snd_hrtimer binfmt_misc usblp autofs4 dm_crypt snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_emu10k1 snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_intel snd_ac97_codec snd_hda_codec ac97_bus snd_pcm snd_util_mem snd_hwdep snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc netconsole configfs firewire_sbp2 emu10k1_gp lp gameport parport psmouse serio_raw joydev dcdbas raid10 raid456 async_pq async_xor async_memcpy async_raid6_recov raid6_pq async_tx raid0 multipath linear dm_raid45 xor raid1 hid_logitech ff_memless hid_microsoft usbhid hid usb_storage uas firewire_ohci firewire_core crc_itu_t radeon ahci libahci ttm drm_kms_helper e1000e drm i2c_algo_bit Architecture: amd64 CheckboxSubmission: fee5e196cb921cbd36888f428b38b488 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Wed Apr 13 11:23:27 2011 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: sudo UpgradeStatus: Upgraded to natty on 2011-04-10 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/760140/+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 1443853] [NEW] Ubuntu 14.10 ISO live boot ends up with a corrupted display
Public bug reported: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10-desktop- amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot ends up with a corrupted display Status in console-setup package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634
[Touch-packages] [Bug 1443853] Re: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display
** Summary changed: - Ubuntu 14.10 ISO live boot ends up with a corrupted display + Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display ** Also affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Virtualbox Trac #13615 http://www.virtualbox.org/ticket/13615 ** Also affects: virtualbox via http://www.virtualbox.org/ticket/13615 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display Status in Virtualbox: Unknown Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
** Summary changed: - Ubuntu 14.10 ISO live boot in VirtualBox ends up with a corrupted display + Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1443853] Re: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display
** Also affects: kbd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu 14.10 ISO live boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: New Status in kbd package in Ubuntu: New Status in virtualbox package in Ubuntu: New Bug description: (Content copied from Ubuntu 14.10 ISO live boot ends up with a corrupted display #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+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 1442915] Re: Missing package installation console output message in gdebi-kde
Bug is not reproducible in gdebi-gtk. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1442915 Title: Missing package installation console output message in gdebi-kde Status in gdebi package in Ubuntu: New Bug description: As attached screenshot, no console output is listed in the Show details textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1442915/+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 1442915] Re: Missing package installation console output message in gdebi-kde
** Summary changed: - Missing package install output message in gdebi-kde + Missing package installation console output message in gdebi-kde -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1442915 Title: Missing package installation console output message in gdebi-kde Status in gdebi package in Ubuntu: New Bug description: As attached screenshot, no console output is listed in the Show details textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1442915/+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 1442915] [NEW] Missing package install output message in gdebi-kde
Public bug reported: As attached screenshot, no console output is listed in the Show details textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty ** Attachment added: Screenshot depicting the bug https://bugs.launchpad.net/bugs/1442915/+attachment/4372485/+files/%E5%AE%8C%E6%88%90%E5%AE%89%E8%A3%9D_481.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1442915 Title: Missing package install output message in gdebi-kde Status in gdebi package in Ubuntu: New Bug description: As attached screenshot, no console output is listed in the Show details textbox during package installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Sat Apr 11 23:35:47 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1442915/+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 1118167] Re: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta-dkms.0.crash'
Bug set to invalid, please reopen the bug if you have other cause of this bug. -- 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/1118167 Title: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta- dkms.0.crash' Status in apport package in Ubuntu: Invalid Bug description: crash after upgrade ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: apport-kde 2.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 17:15:24 2013 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2012-10-31 (98 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/share/apport/apport-kde'] SourcePackage: apport Title: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta-dkms.0.crash' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1118167/+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 1118167] Re: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta-dkms.0.crash'
I believe this is because that broadcom-sta-dkms is run as root (thus created a crash file at /var/crash owned as root) but you tried to read it as a normal user? If it is the case then it's not crash but an error that you should run apport-kde as root in order to process that crash file. ** Changed in: apport (Ubuntu) Status: Confirmed = Invalid -- 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/1118167 Title: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta- dkms.0.crash' Status in apport package in Ubuntu: Invalid Bug description: crash after upgrade ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: apport-kde 2.8-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-4.9-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 17:15:24 2013 ExecutablePath: /usr/share/apport/apport-kde InstallationDate: Installed on 2012-10-31 (98 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-kde ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/share/apport/apport-kde'] SourcePackage: apport Title: apport-kde crashed with PermissionError in thread_collect_info(): [Errno 1] Operation not permitted: '/var/crash/broadcom-sta-dkms.0.crash' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1118167/+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 1438698] [NEW] [packaging?] apport-kde depends on python3-pykde4, but it seems trying to import it's python2.7 version(Error: No module named PyKDE4.kdecore)
Public bug reported: Hi when I tried to run python /usr/share/apport/apport-kde 1438689 it fails with the following message: ``` ... import PyQt4.uic.Compiler.qobjectcreator # precompiled from /usr/lib/python2.7/dist-packages/PyQt4/uic/Compiler/qobjectcreator.pyc ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyKDE4.kdecore ``` It seems that apport-kde tries to import python2 version's pykde4.kdecore but failed because the package actually depends on python3 version. After I install python-kde4 package the error vanishes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-kde 2.14.1-0ubuntu3.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Tue Mar 31 21:38:17 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 packaging third-party-packages trusty ** Description changed: - Hi when I tried to ran python /usr/share/apport/apport-kde 1438689 it fails with the following message: + Hi when I tried to run python /usr/share/apport/apport-kde 1438689 it fails with the following message: ``` ... import PyQt4.uic.Compiler.qobjectcreator # precompiled from /usr/lib/python2.7/dist-packages/PyQt4/uic/Compiler/qobjectcreator.pyc ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyKDE4.kdecore ``` It seems that apport-kde tries to import python2 version's pykde4.kdecore but failed because the package actually depends on python3 version. After I install python-kde4 package the error vanishes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-kde 2.14.1-0ubuntu3.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Tue Mar 31 21:38:17 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1438698 Title: [packaging?] apport-kde depends on python3-pykde4, but it seems trying to import it's python2.7 version(Error: No module named PyKDE4.kdecore) Status in apport package in Ubuntu: New Bug description: Hi when I tried to run python /usr/share/apport/apport-kde 1438689 it fails with the following message: ``` ... import PyQt4.uic.Compiler.qobjectcreator # precompiled from /usr/lib/python2.7/dist-packages/PyQt4/uic/Compiler/qobjectcreator.pyc ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyKDE4.kdecore ``` It seems that apport-kde tries to import python2 version's pykde4.kdecore but failed because the package actually depends on python3 version. After I install python-kde4 package the error vanishes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-kde 2.14.1-0ubuntu3.8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.8 Architecture: i386 CurrentDesktop: KDE Date: Tue Mar 31 21:38:17 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1438698/+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 856269] Re: lightdm does not ask for a new password with pam_winbind or pam_krb5 authentications when the password is expired
This bug is still present in trusty. -- 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/856269 Title: lightdm does not ask for a new password with pam_winbind or pam_krb5 authentications when the password is expired Status in lightdm package in Ubuntu: Confirmed Bug description: I'm using an up-to-date oneiric workstation joined through samba and winbind to an AD domain controlled by a Windows server. When the password of a domain user is expired and when pam_winbind is used as first authentication, lightdm does not ask for a new password and does not allow to login, displaying the message Invalid password, please try again. Instead, when pam_krb5 is used as first authentication, lightdm asks two times for a password (Enter it again:) and then allows to login even if the password is expired. When using a text console to login, the password changing dialog is immediately presented (as it happens in natty with gdm). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/856269/+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 1262202] Re: ubuntu-bug tomcat7 is crashing with permission denied
Confirmed this issue on gdebi-kde package -- 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/1262202 Title: ubuntu-bug tomcat7 is crashing with permission denied Status in apport package in Ubuntu: Confirmed Bug description: On Ubuntu 12.04 i wanted to report a bug against tomcat7, so i used ubuntu-bug tomcat7 and i got this traceback: The first two german lines are just collecting information can be send to the developers to improve the application Die gesammelten Informationen können an die Entwickler gesendet werden um die Anwendung zu verbessern. Dies kann einige Minuten dauern. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport/report.py, line 719, in add_hooks_info symb['add_info'](self, ui) File /usr/share/apport/general-hooks/ubuntu.py, line 92, in add_info attach_conffiles(report, package, ui=ui) File /usr/lib/python2.7/dist-packages/apport/hookutils.py, line 107, in attach_conffiles modified = packaging.get_modified_conffiles(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 263, in get_modified_conffiles with open(path, 'rb') as fd: IOError: [Errno 13] Permission denied: u'/etc/tomcat7/tomcat-users.xml' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tomcat7 7.0.26-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.5.0-43.66~precise1-generic 3.5.7.23 Uname: Linux 3.5.0-43-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 18 14:04:59 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: tomcat7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262202/+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 1411523] [NEW] apport-bug/ubuntu-bug generates confusing error when crash file cannot be read
Public bug reported: ## Reproduce steps apport-bug/ubuntu-bug a .crash file that is not readable by you ## Current behavior A window popped out with Permission denied as error message. ## Expected behavior A much descriptive error like: * Cannot access the crash file: Permission denied. * Cannot access the crash file: Permission denied. Crash file can only be accessed by the generating user or administrator because it may contain confidential data. (better) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.6 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: KDE Date: Fri Jan 16 14:41:20 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty -- 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/1411523 Title: apport-bug/ubuntu-bug generates confusing error when crash file cannot be read Status in apport package in Ubuntu: New Bug description: ## Reproduce steps apport-bug/ubuntu-bug a .crash file that is not readable by you ## Current behavior A window popped out with Permission denied as error message. ## Expected behavior A much descriptive error like: * Cannot access the crash file: Permission denied. * Cannot access the crash file: Permission denied. Crash file can only be accessed by the generating user or administrator because it may contain confidential data. (better) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.6 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: KDE Date: Fri Jan 16 14:41:20 2015 PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1411523/+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 1262202] Re: ubuntu-bug tomcat7 is crashing with permission denied
UPDATE: Taking closer look to the bug I find out that it's isn't really my issue. -- 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/1262202 Title: ubuntu-bug tomcat7 is crashing with permission denied Status in apport package in Ubuntu: Confirmed Bug description: On Ubuntu 12.04 i wanted to report a bug against tomcat7, so i used ubuntu-bug tomcat7 and i got this traceback: The first two german lines are just collecting information can be send to the developers to improve the application Die gesammelten Informationen können an die Entwickler gesendet werden um die Anwendung zu verbessern. Dies kann einige Minuten dauern. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport/report.py, line 719, in add_hooks_info symb['add_info'](self, ui) File /usr/share/apport/general-hooks/ubuntu.py, line 92, in add_info attach_conffiles(report, package, ui=ui) File /usr/lib/python2.7/dist-packages/apport/hookutils.py, line 107, in attach_conffiles modified = packaging.get_modified_conffiles(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 263, in get_modified_conffiles with open(path, 'rb') as fd: IOError: [Errno 13] Permission denied: u'/etc/tomcat7/tomcat-users.xml' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tomcat7 7.0.26-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.5.0-43.66~precise1-generic 3.5.7.23 Uname: Linux 3.5.0-43-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 18 14:04:59 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: tomcat7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262202/+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 1411531] [NEW] gdebi-kde crashed with SIGSEGV in QWidget::~QWidget() when installing a Debian package
Public bug reported: as Summary and apport report ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: KDE Date: Fri Jan 16 15:04:55 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty ** Attachment added: apport_report.txt https://bugs.launchpad.net/bugs/1411531/+attachment/4299762/+files/apport_report.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1411531 Title: gdebi-kde crashed with SIGSEGV in QWidget::~QWidget() when installing a Debian package Status in gdebi package in Ubuntu: New Bug description: as Summary and apport report ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gdebi-kde 0.9.5.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CurrentDesktop: KDE Date: Fri Jan 16 15:04:55 2015 PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1411531/+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 1330239] Re: Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid showed in syslog in Ubuntu 14.04
** Changed in: modemmanager (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1330239 Title: Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid showed in syslog in Ubuntu 14.04 Status in modemmanager package in Ubuntu: Invalid Bug description: as bug summary ` dbus[pid]: [system] Activating service name='org.freedesktop.ModemManager1' (using servicehelper) dbus[pid]: [system] Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid ` appears every 2 minutes ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: modemmanager 1.0.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-lowlatency 3.13.11.2 Uname: Linux 3.13.0-29-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Mon Jun 16 01:50:38 2014 InstallationDate: Installed on 2013-03-08 (463 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: modemmanager UpgradeStatus: Upgraded to trusty on 2014-04-19 (57 days ago) upstart.modemmanager.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1330239/+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 1330239] Re: Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid showed in syslog in Ubuntu 14.04
I found that this message generated because I manually disabled the modemmanager Upstart service, which isn't a bug since NetworkManager needs it anyway. The motivation of disabling this service is that it's starts no matter if there's modem connected and it abnormally generates redundant restart messages during system shutdown, if anyone have concern of this issue please file a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1330239 Title: Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid showed in syslog in Ubuntu 14.04 Status in modemmanager package in Ubuntu: Invalid Bug description: as bug summary ` dbus[pid]: [system] Activating service name='org.freedesktop.ModemManager1' (using servicehelper) dbus[pid]: [system] Activated service 'org.freedesktop.ModemManager1' failed: Cannot launch daemon, file not found or permissions invalid ` appears every 2 minutes ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: modemmanager 1.0.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.53-lowlatency 3.13.11.2 Uname: Linux 3.13.0-29-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CurrentDesktop: KDE Date: Mon Jun 16 01:50:38 2014 InstallationDate: Installed on 2013-03-08 (463 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: modemmanager UpgradeStatus: Upgraded to trusty on 2014-04-19 (57 days ago) upstart.modemmanager.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1330239/+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 1391265] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1391265/+attachment/4258179/+files/ProcEnviron.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258178/+files/Dependencies.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258179/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1,
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
apport information ** Tags added: apport-collected third-party-packages trusty ** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 #19 0x0040945e in ?? () #20 0x004097f8 in ?? () #21 0x00408c30 in ?? () #22 0x74fe5ec5 in __libc_start_main (main=0x408c20, argc=1, argv=0x7fffdd28, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffdd18) at libc-start.c:287 #23 0x00408c60 in ?? ()
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
Oops, apport-collect on a wrong computer. ** Tags removed: apport-collected third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 #19 0x0040945e in ?? ()
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
** Bug watch added: IBus bugs #1748 http://code.google.com/p/ibus/issues/detail?id=1748 ** Also affects: ibus via http://code.google.com/p/ibus/issues/detail?id=1748 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in IBus: Unknown Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
apport information ** Tags added: apport-collected ** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 #19 0x0040945e in ?? () #20 0x004097f8 in ?? () #21 0x00408c30 in ?? () #22 0x74fe5ec5 in __libc_start_main (main=0x408c20, argc=1, argv=0x7fffdd28, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffdd18) at libc-start.c:287 #23 0x00408c60 in ?? () (gdb) ` ##
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
** Attachment added: Generated file under /var/crash https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258416/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in IBus: Unknown Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045
[Touch-packages] [Bug 1391265] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1391265/+attachment/4258415/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in IBus: Unknown Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
** Attachment added: .crash file after apport-retrace https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258507/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in IBus: Unknown Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18
[Touch-packages] [Bug 1242113] Re: Cannot input chinese in Unity Dash or HUD using fcitx input method.
Hi, Unity Dash should support input method now since bug 983254 is fixed. ** Changed in: unity Status: New = Invalid ** Changed in: unity Status: Invalid = Fix Released ** Changed in: unity (Ubuntu) Status: New = 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/1242113 Title: Cannot input chinese in Unity Dash or HUD using fcitx input method. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Cannot change input method engine into any Chinese one under the Unity Dash or HUD interface. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1242113/+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 1391265] [NEW] ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.04
Public bug reported: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Workarounds Currently there's no workaround, set keybinding back to default value didn't work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 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: KDE Date: Tue Nov 11 01:54:35 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Summary changed: - ibus-ui-gtk3 crashed after changing keybinding in Kubuntu14.04 + ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.04 ** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log + ## Workarounds + Currently there's no workaround, set keybinding back to default value didn't work. + ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 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: KDE Date: Tue Nov 11 01:54:35 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.04 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Workarounds Currently there's no workaround, set keybinding back to default value didn't work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ibus 1.5.8-2ubuntu2 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: KDE Date: Tue Nov 11 01:54:35 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+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 1391265] Re: ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.04
** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log + + ## Stacktrace + ` + (gdb) run + Starting program: /usr/lib/ibus/ibus-ui-gtk3 + [Thread debugging using libthread_db enabled] + Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. + [New Thread 0x7fffedbad700 (LWP 6386)] + [New Thread 0x7fffed3ac700 (LWP 6387)] + [New Thread 0x7fffecbab700 (LWP 6389)] + + (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. + This probably reflects a bug in the program. + The error was 'BadValue (integer parameter out of range for operation)'. + (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) + (Note to programmers: normally, X errors are reported asynchronously; +that is, you will receive the error a while after causing it. +To debug your program, run it with the GDK_SYNCHRONIZE environment +variable to change this behavior. You can then get a meaningful +backtrace from your debugger if you break on the gdk_x_error() function.) + + Program received signal SIGTRAP, Trace/breakpoint trap. + g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, + args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 + 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. + (gdb) bt + #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, + format=optimized out, args=args@entry=0x7fffd510) + at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 + #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, + log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) + at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 + #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, + error=error@entry=0x7fffd6c0) + at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 + #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) + at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 + #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) + at ../../src/XlibInt.c:1463 + #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, + in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 + #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, + extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 + #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, + grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, + grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, + modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 + #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, + keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, + paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, + modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 + #9 0x0040dffe in ?? () + #10 0x00411385 in ?? () + #11 0x00412d66 in ?? () + #12 0x00408f5d in ?? () + #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) + at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 + #14 0x755f0b6d in g_main_dispatch (context=0x673e20) + at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 + #15 g_main_context_dispatch (context=context@entry=0x673e20) + at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 + #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, + dispatch=dispatch@entry=1, self=optimized out) + at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 + #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) + at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 + #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 + #19 0x0040945e in ?? () + #20 0x004097f8 in ?? () + #21 0x00408c30 in ?? () + #22 0x74fe5ec5 in __libc_start_main (main=0x408c20, argc=1, argv=0x7fffdd28, + init=optimized out, fini=optimized out, rtld_fini=optimized out, + stack_end=0x7fffdd18) at libc-start.c:287 + #23 0x00408c60 in ?? () + (gdb) + ` ## Workarounds Currently there's no
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.10
** Summary changed: - ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.04 + ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.10 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu14.10
** Summary changed: - ibus-ui-gtk3 crashed right after changing keybinding in Kubuntu14.10 + ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu14.10 ** Summary changed: - ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu14.10 + ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 ** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log - ## Stacktrace + ## Stacktrace ` (gdb) run - Starting program: /usr/lib/ibus/ibus-ui-gtk3 + Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. - (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) - (Note to programmers: normally, X errors are reported asynchronously; -that is, you will receive the error a while after causing it. -To debug your program, run it with the GDK_SYNCHRONIZE environment -variable to change this behavior. You can then get a meaningful -backtrace from your debugger if you break on the gdk_x_error() function.) + (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) + (Note to programmers: normally, X errors are reported asynchronously; + that is, you will receive the error a while after causing it. + To debug your program, run it with the GDK_SYNCHRONIZE environment + variable to change this behavior. You can then get a meaningful + backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. - g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, - args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 + g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, + args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt - #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, - format=optimized out, args=args@entry=0x7fffd510) - at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 - #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, - log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) - at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 - #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, - error=error@entry=0x7fffd6c0) - at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 + #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, + format=optimized out, args=args@entry=0x7fffd510) + at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 + #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, + log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) + at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 + #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, + error=error@entry=0x7fffd6c0) + at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) - at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 + at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) - at ../../src/XlibInt.c:1463 - #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, - in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 - #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, - extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 - #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, - grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, - grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980,
[Touch-packages] [Bug 1388558] [NEW] [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04
Public bug reported: The following message printed when I run '$ compiz --replace' in the terminal: ` ERROR unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: Can't open shared object file: File not found ` It seems that Unity(or it's component) depends on this library but however, not installed with unity package. Manually install libxpathselect1.4 package removes that error message. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Nov 2 21:16:26 2014 InstallationDate: Installed on 2013-03-08 (603 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (197 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug gnome3-ppa i386 third-party-packages trusty -- 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/1388558 Title: [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04 Status in “unity” package in Ubuntu: New Bug description: The following message printed when I run '$ compiz --replace' in the terminal: ` ERROR unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: Can't open shared object file: File not found ` It seems that Unity(or it's component) depends on this library but however, not installed with unity package. Manually install libxpathselect1.4 package removes that error message. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Nov 2 21:16:26 2014 InstallationDate: Installed on 2013-03-08 (603 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1388558/+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 1388558] Re: [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04
Thanks for the explaination :-) -- 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/1388558 Title: [packaging]Missing dependency to libxpathselect1.4 in Ubuntu 14.04 Status in “unity” package in Ubuntu: Won't Fix Bug description: The following message printed when I run '$ compiz --replace' in the terminal: ` ERROR unity.debug.interface DebugDBusInterface.cpp:216 Unable to load entry point in libxpathselect: libxpathselect.so.1.4: Can't open shared object file: File not found ` It seems that Unity(or it's component) depends on this library but however, not installed with unity package. Manually install libxpathselect1.4 package removes that error message. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: KDE Date: Sun Nov 2 21:16:26 2014 InstallationDate: Installed on 2013-03-08 (603 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-19 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1388558/+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 1387825] [NEW] The default NAME_REGEX value in /etc/adduser.conf is incorrect
Public bug reported: Refer the Debian bug report for more information. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: adduser 3.113+nmu3ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 31 01:55:03 2014 InstallationDate: Installed on 2013-03-08 (600 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago) ** Affects: adduser (Ubuntu) Importance: Undecided Status: New ** Affects: adduser (Debian) Importance: Unknown Status: Unknown ** Tags: apport-bug i386 trusty ** Bug watch added: Debian Bug tracker #630750 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750 ** Also affects: adduser (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1387825 Title: The default NAME_REGEX value in /etc/adduser.conf is incorrect Status in “adduser” package in Ubuntu: New Status in “adduser” package in Debian: Unknown Bug description: Refer the Debian bug report for more information. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: adduser 3.113+nmu3ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-22.29-lowlatency 3.16.4 Uname: Linux 3.16.0-22-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: KDE Date: Fri Oct 31 01:55:03 2014 InstallationDate: Installed on 2013-03-08 (600 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) PackageArchitecture: all SourcePackage: adduser UpgradeStatus: Upgraded to trusty on 2014-04-19 (194 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1387825/+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 1072556] Re: Can not adduser with just number
No, NAME_REGEX is or not commented out doesn't mean adduser didn't have a default NAME_REGEX setting, in fact when NAME_REGEX is uncommented it should overwrite adduser's default setting and let the magic work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to adduser in Ubuntu. https://bugs.launchpad.net/bugs/1072556 Title: Can not adduser with just number Status in “adduser” package in Ubuntu: New Bug description: Was trying to add a user via adduser with just the username of 1600 and the following is displayed: adduser: Please enter a username matching the regular expression configured via the NAME_REGEX[_SYSTEM] configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. I checked the options fore the NAME_REGEX in /etc/adduser.conf and it is commented out and shouldn't be affecting the adduser command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1072556/+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 1373495] [NEW] sudo shouldn't preserve HOME environment variable by default
Public bug reported: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue is in this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Description changed: Currently Ubuntu hard-coded preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when user run the same program using it's account and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help - Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tell that + Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't launch by sudo, but in fact the real issue is in this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: - /etc/sudoers: parsed OK - /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK - /etc/sudoers.d/README: parsed OK + /etc/sudoers: parsed OK + /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK + /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 ** Description changed: - Currently Ubuntu hard-coded preserve HOME environment variable to point - to sudo caller's home directory by default(refer bug #760140) however - this is dangerous and error-prone because the program run by root may - write files (e.g. $HOME/.Xauthority , program config files) into the - HOME directory **AS ROOT** which, will cause issue when user run the - same program using it's account and even make the user failed to + Currently Ubuntu hard-coded sudo to preserve HOME environment variable + to point to sudo caller's home directory by default(refer bug #760140) + however this is dangerous and error-prone because the program run by + root may write files (e.g. $HOME/.Xauthority , program config files) + into the HOME directory **AS ROOT** which, will cause issue when users + run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration
[Touch-packages] [Bug 501204] Re: sudo syntax error in /etc/sudoers due to #-- comment
** Description changed: - Binary package hint: network-manager + Binary package hint: sudo I put a few comments in /etc/sudoers where the '#' comment char is succeeded with -- as in: #--ariel--# result: sudo won't work anymore. - $ sudo echo OK - /etc/sudoers: syntax error near line 9 - /etc/sudoers: syntax error near line 27 - sudo: parse error in /etc/sudoers near line 9 - sudo: no valid sudoers sources found, quitting + $ sudo echo OK + /etc/sudoers: syntax error near line 9 + /etc/sudoers: syntax error near line 27 + sudo: parse error in /etc/sudoers near line 9 + sudo: no valid sudoers sources found, quitting putting a space between the '#' and '--' solves the problem. Comments should start with '#' only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/501204 Title: sudo syntax error in /etc/sudoers due to #-- comment Status in “sudo” package in Ubuntu: Confirmed Bug description: Binary package hint: sudo I put a few comments in /etc/sudoers where the '#' comment char is succeeded with -- as in: #--ariel--# result: sudo won't work anymore. $ sudo echo OK /etc/sudoers: syntax error near line 9 /etc/sudoers: syntax error near line 27 sudo: parse error in /etc/sudoers near line 9 sudo: no valid sudoers sources found, quitting putting a space between the '#' and '--' solves the problem. Comments should start with '#' only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/501204/+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 1373495] Re: sudo shouldn't preserve HOME environment variable by default
** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration - by default), any user wish to run command as root using their HOME - directory should set env_keep in /etc/sudoers themselves and + to generic users by default), any user wish to run command as root using + their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue is in this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 ** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration - to generic users by default), any user wish to run command as root using + to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue is in this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve HOME environment variable by default Status in “sudo” package in Ubuntu: New Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves
[Touch-packages] [Bug 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Summary changed: - sudo shouldn't preserve HOME environment variable by default + sudo shouldn't preserve caller's HOME environment variable by default -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in “sudo” package in Ubuntu: New Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue is in this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373495/+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 1373521] [NEW] Environment variables used by input methods should be preserved.
Public bug reported: Input method under GNU/Linux relies on several environment variables to work properly, setting the following sudoers config by default will enable input method in applications run as other users: Defaultsenv_keep += GTK_IM_MODULE Defaultsenv_keep += QT_IM_MODULE Defaultsenv_keep += QT4_IM_MODULE Defaultsenv_keep += CLUTTER_IM_MODULE Defaultsenv_keep += XMODIFIERS Thanks in advance! ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Description changed: Input method under GNU/Linux relies on several environment variables to - work properly, please set the following sudoers config by default: + work properly, setting the following sudoers config by default will + enable input method in applications run as other users: Defaults env_keep += GTK_IM_MODULE Defaults env_keep += QT_IM_MODULE Defaults env_keep += QT4_IM_MODULE Defaults env_keep += CLUTTER_IM_MODULE Defaults env_keep += XMODIFIERS Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373521 Title: Environment variables used by input methods should be preserved. Status in “sudo” package in Ubuntu: New Bug description: Input method under GNU/Linux relies on several environment variables to work properly, setting the following sudoers config by default will enable input method in applications run as other users: Defaults env_keep += GTK_IM_MODULE Defaults env_keep += QT_IM_MODULE Defaults env_keep += QT4_IM_MODULE Defaults env_keep += CLUTTER_IM_MODULE Defaults env_keep += XMODIFIERS Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373521/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real - issue is in this bug. + issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in “sudo” package in Ubuntu: New Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373495/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) - In my opinion the Ubuntu patch that make $HOME variable keep in sudo is - INSANE and should be reverted(Ubuntu should use the safest configuration - to general users by default), any user wish to run command as root using - their HOME directory should set env_keep in /etc/sudoers themselves and - acknowledging the consequences. + In my opinion the Ubuntu patch(keep_home_by_default.patch) that make + $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu + should use the safest configuration to general users by default), any + user wish to run command as root using their HOME directory should set + env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in “sudo” package in Ubuntu: New Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into the HOME directory **AS ROOT** which, will cause issue when users run the same program as themselves and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch) that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373495/+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 1373495] Re: sudo shouldn't preserve caller's HOME environment variable by default
** Description changed: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) - into the HOME directory **AS ROOT** which, will cause issue when users - run the same program as themselves and even make the user failed to - login(due to .Xauthority file owner is incorrect) + into caller's HOME directory **AS ROOT** which, will cause issue when + users run the same program as their normal users' account again and even + make the user failed to login(due to .Xauthority file owner is + incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch) that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1373495 Title: sudo shouldn't preserve caller's HOME environment variable by default Status in “sudo” package in Ubuntu: Confirmed Bug description: Currently Ubuntu hard-coded sudo to preserve HOME environment variable to point to sudo caller's home directory by default(refer bug #760140) however this is dangerous and error-prone because the program run by root may write files (e.g. $HOME/.Xauthority , program config files) into caller's HOME directory **AS ROOT** which, will cause issue when users run the same program as their normal users' account again and even make the user failed to login(due to .Xauthority file owner is incorrect) In my opinion the Ubuntu patch(keep_home_by_default.patch) that make $HOME variable keep in sudo is INSANE and should be reverted(Ubuntu should use the safest configuration to general users by default), any user wish to run command as root using their HOME directory should set env_keep in /etc/sudoers themselves and acknowledging the consequences. RootSudo - Community Help Wiki(https://help.ubuntu.com/community/RootSudo ) wrongly tells that graphical application shouldn't be launch by sudo, but in fact the real issue falls into this bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-lowlatency 3.16.3 Uname: Linux 3.16.0-17-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Thu Sep 25 00:08:44 2014 InstallationDate: Installed on 2013-03-08 (564 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: sudo UpgradeStatus: Upgraded to trusty on 2014-04-19 (158 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/Preserve_input_method_required_environmental_variables: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers.d.README: [modified] mtime.conffile..etc.sudoers.d.README: 2014-09-24T22:26:35.734703 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1373495/+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 1372265] [NEW] [packaging] /etc/bluetooth/*.conf appears during unpacking but disappeared after package installed
Public bug reported: Hi, I found that bluez config files under /etc/bluetooth were gone and tried to reinstall them using # apt-get install --reinstall bluez ; , then I noticed that those files appeared (as *.conf.dpkg-new) during package unpacking state but disappeared again after the package was installed. I suspected that there's issue in the package install/postinstall script. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-13.19-lowlatency 3.16.1 Uname: Linux 3.16.0-13-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Mon Sep 22 13:40:15 2014 InstallationDate: Installed on 2013-03-08 (562 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) InterestingModules: rfcomm btusb bnep bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-lowlatency root=UUID=a2700cc1-7ea8-4572-ae5e-f364ee6cb619 ro crashkernel=384M-2G:64M,2G-:128M splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-04-19 (156 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN RX bytes:48439842 acl:151 sco:949426 events:2090 errors:0 TX bytes:49081906 acl:2290 sco:949394 commands:83 errors:0 rfkill: 1: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty ** Summary changed: - [packaging] /etc/bluetooth/*.conf appears when unpacking but disappeared after package installed + [packaging] /etc/bluetooth/*.conf appears during unpacking but disappeared after package installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1372265 Title: [packaging] /etc/bluetooth/*.conf appears during unpacking but disappeared after package installed Status in “bluez” package in Ubuntu: New Bug description: Hi, I found that bluez config files under /etc/bluetooth were gone and tried to reinstall them using # apt-get install --reinstall bluez ; , then I noticed that those files appeared (as *.conf.dpkg-new) during package unpacking state but disappeared again after the package was installed. I suspected that there's issue in the package install/postinstall script. Thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.16.0-13.19-lowlatency 3.16.1 Uname: Linux 3.16.0-13-lowlatency i686 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CurrentDesktop: KDE Date: Mon Sep 22 13:40:15 2014 InstallationDate: Installed on 2013-03-08 (562 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) InterestingModules: rfcomm btusb bnep bluetooth MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-lowlatency root=UUID=a2700cc1-7ea8-4572-ae5e-f364ee6cb619 ro crashkernel=384M-2G:64M,2G-:128M splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-04-19 (156 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:15:83:54:59:9F ACL MTU: 310:10 SCO
[Touch-packages] [Bug 1364173]
I found out that kdm runs /etc/kde4/kdm/Xsession using user's default shell. http://i.imgur.com/xyiJ1b8.jpg It is not sane as in Xsession(5) manpage notes: /etc/X11/Xsession is a Bourne shell (sh(1)) script which is run when an X Window System session is begun by startx(1) or a display manager such as xdm(1). -- 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/1364173 Title: Xsession sourced scripts shouldn't be run using user's default shell Status in KDE Base Workspace: New Status in “kde-workspace” package in Ubuntu: New Status in “xorg” package in Ubuntu: Invalid Bug description: Recently I encountered a problem that my input method malfunctions because the environmental variables are wrongly set(which is, fully configured using im-config), after hours of debugging I found that it's Z-shell(my current default shell)'s bug that prematurely quits before the Xsession.d im-config input method configure script completes. The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) **shouldn't** be run in Z-shell. Patching /etc/kde4/kdm/Xsession # invoke global X session script. code from . /etc/X11/Xsession to /etc/X11/Xsession workarounded the issue (however I have no idea why). Switching to other display managers instead of KDM worked also) Reproducible: Always Steps to Reproduce: Currently there's no simple reproduce method as another software(zsh)'s bug involved. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1364173/+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 1364173]
Here's the Zsh bug report end that Zsh is behave properly, but not the same way as Bash do. Z-Shell breaks im-config configuration scripts, making input method malfunction http://www.zsh.org/mla/workers/2014/msg00886.html -- 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/1364173 Title: Xsession sourced scripts shouldn't be run using user's default shell Status in KDE Base Workspace: New Status in “kde-workspace” package in Ubuntu: New Status in “xorg” package in Ubuntu: Invalid Bug description: Recently I encountered a problem that my input method malfunctions because the environmental variables are wrongly set(which is, fully configured using im-config), after hours of debugging I found that it's Z-shell(my current default shell)'s bug that prematurely quits before the Xsession.d im-config input method configure script completes. The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) **shouldn't** be run in Z-shell. Patching /etc/kde4/kdm/Xsession # invoke global X session script. code from . /etc/X11/Xsession to /etc/X11/Xsession workarounded the issue (however I have no idea why). Switching to other display managers instead of KDM worked also) Reproducible: Always Steps to Reproduce: Currently there's no simple reproduce method as another software(zsh)'s bug involved. To manage notifications about this bug go to: https://bugs.launchpad.net/kdebase-workspace/+bug/1364173/+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 1364173] [NEW] Xsession sourced scripts shouldn't be run using user's default shell
Public bug reported: Recently I encountered a problem that my input method malfunction because the environmental variables are wrongly set(but it is fully configured using im-config), after hours of debugging I found that it's Z-shell(my current default shell)'s bug that prematurely quit the im- config input method configure Xsession.d script. While that's another Z-shell's bug, the problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) **shouldn't** run in Z-shell. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: x11-common 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6 Uname: Linux 3.13.0-35-lowlatency i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] 是個目錄: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 331.38 Wed Jan 8 18:44:57 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin CurrentDesktop: KDE Date: Tue Sep 2 07:18:58 2014 DistUpgraded: 2014-04-19 12:12:02,233 DEBUG fork pid is: 0 DistroCodename: trusty DistroVariant: kubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:34e7] InstallationDate: Installed on 2013-03-08 (542 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: System manufacturer System Product Name PackageArchitecture: all ProcKernelCmdLine: root=UUID=aa9c6442-c0f4-4544-9f01-706d10aee605 ro crashkernel=384M-2G:64M,2G-:128M splash crashkernel=384M-:128M SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-19 (135 days ago) dmi.bios.date: 08/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P7H55-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.56+git1408251830.391bba~gd~t version.libgl1-mesa-dri: libgl1-mesa-dri 10.4~git1408311930.e34a36~gd~t version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4~git1408311930.e34a36~gd~t 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.4.99+git1408211931.ba5fcc~gd~t version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914+git1408311930.2c564c~gd~t version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1408170730.16c885~gd~t xserver.bootTime: Tue Sep 2 07:05:53 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 kubuntu trusty -- 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/1364173 Title: Xsession sourced scripts shouldn't be run using user's default shell Status in “xorg” package in Ubuntu: New Bug description: Recently I encountered a problem that my input method malfunction because the environmental variables are wrongly set(but it is fully configured using im-config), after hours of debugging I found that it's Z-shell(my current default shell)'s bug that prematurely quit the im-config input method configure Xsession.d script. While that's another Z-shell's bug, the problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) **shouldn't** run in Z-shell. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: x11-common 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6 Uname: Linux 3.13.0-35-lowlatency i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] 是個目錄: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version:
[Touch-packages] [Bug 1364173] Re: Xsession sourced scripts shouldn't be run using user's default shell
** Bug watch added: KDE Bug Tracking System #338740 https://bugs.kde.org/show_bug.cgi?id=338740 ** Also affects: kdebase-workspace via https://bugs.kde.org/show_bug.cgi?id=338740 Importance: Unknown Status: Unknown ** Description changed: Recently I encountered a problem that my input method malfunctions - because the environmental variables are wrongly set(but it is fully + because the environmental variables are wrongly set(which is, fully configured using im-config), after hours of debugging I found that it's Z-shell(my current default shell)'s bug that prematurely quits before the Xsession.d im-config input method configure script completes. - While that's another Z-shell's bug, the problem is, /etc/X11/Xsession - (and all the Xsession.d scripts it sourced) **shouldn't** run in - Z-shell. + The problem is, /etc/X11/Xsession (and all the Xsession.d scripts it sourced) **shouldn't** be run in Z-shell. Patching /etc/kde4/kdm/Xsession # invoke global X session script. code from + . /etc/X11/Xsession + to + /etc/X11/Xsession - ProblemType: Bug - DistroRelease: Ubuntu 14.04 - Package: x11-common 1:7.7+1ubuntu8 - ProcVersionSignature: Ubuntu 3.13.0-35.62-lowlatency 3.13.11.6 - Uname: Linux 3.13.0-35-lowlatency i686 - NonfreeKernelModules: nvidia - .proc.driver.nvidia.gpus.0: Error: [Errno 21] 是個目錄: '/proc/driver/nvidia/gpus/0' - .proc.driver.nvidia.registry: Binary: - .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86 Kernel Module 331.38 Wed Jan 8 18:44:57 PST 2014 - GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) - .tmp.unity.support.test.0: + workarounded the issue (however I have no idea why). Switching to other + display managers instead of KDM worked also) - ApportVersion: 2.14.1-0ubuntu3.3 - Architecture: i386 - CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' - CompositorRunning: kwin - CurrentDesktop: KDE - Date: Tue Sep 2 07:18:58 2014 - DistUpgraded: 2014-04-19 12:12:02,233 DEBUG fork pid is: 0 - DistroCodename: trusty - DistroVariant: kubuntu - ExtraDebuggingInterest: I just need to know a workaround - GraphicsCard: - NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) - Subsystem: Gigabyte Technology Co., Ltd Device [1458:34e7] - InstallationDate: Installed on 2013-03-08 (542 days ago) - InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) - MachineType: System manufacturer System Product Name - PackageArchitecture: all - ProcKernelCmdLine: root=UUID=aa9c6442-c0f4-4544-9f01-706d10aee605 ro crashkernel=384M-2G:64M,2G-:128M splash crashkernel=384M-:128M - SourcePackage: xorg - UpgradeStatus: Upgraded to trusty on 2014-04-19 (135 days ago) - dmi.bios.date: 08/18/2010 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: 1101 - dmi.board.asset.tag: To Be Filled By O.E.M. - dmi.board.name: P7H55-M - dmi.board.vendor: ASUSTeK Computer INC. - dmi.board.version: Rev X.0x - dmi.chassis.asset.tag: Asset-1234567890 - dmi.chassis.type: 3 - dmi.chassis.vendor: Chassis Manufacture - dmi.chassis.version: Chassis Version - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd08/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7H55-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: - dmi.product.name: System Product Name - dmi.product.version: System Version - dmi.sys.vendor: System manufacturer - version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 - version.libdrm2: libdrm2 2.4.56+git1408251830.391bba~gd~t - version.libgl1-mesa-dri: libgl1-mesa-dri 10.4~git1408311930.e34a36~gd~t - version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A - version.libgl1-mesa-glx: libgl1-mesa-glx 10.4~git1408311930.e34a36~gd~t - 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.4.99+git1408211931.ba5fcc~gd~t - version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914+git1408311930.2c564c~gd~t - version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git1408170730.16c885~gd~t - xserver.bootTime: Tue Sep 2 07:05:53 2014 - xserver.configfile: /etc/X11/xorg.conf - xserver.errors: + Reproducible: Always - xserver.logfile: /var/log/Xorg.0.log - xserver.outputs: - - xserver.version: 2:1.15.1-0ubuntu2 + Steps to Reproduce: + Currently there's no simple reproduce method as another software(zsh)'s bug involved. -- 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/1364173 Title: Xsession sourced scripts shouldn't be run using user's default shell Status in KDE Base Workspace: Unknown Status in “kde-workspace”
[Touch-packages] [Bug 1362314] [NEW] Failed to input content using input method
Public bug reported: I can't input anything using input method, input method isn't activated and only English is inserted ## Reporter's environment ### Input method HIME ### locale zh_TW.UTF-8 ### Operating system Ubuntu 14.04 x86 32-bit ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webapp-container 0.23+14.04.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-34.60-lowlatency 3.13.11.4 Uname: Linux 3.13.0-34-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CurrentDesktop: Unity Date: Thu Aug 28 04:01:16 2014 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2013-03-08 (536 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: webbrowser-app UpgradeStatus: Upgraded to trusty on 2014-04-19 (130 days ago) ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 third-party-packages trusty -- 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/1362314 Title: Failed to input content using input method Status in “webbrowser-app” package in Ubuntu: New Bug description: I can't input anything using input method, input method isn't activated and only English is inserted ## Reporter's environment ### Input method HIME ### locale zh_TW.UTF-8 ### Operating system Ubuntu 14.04 x86 32-bit ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webapp-container 0.23+14.04.20140428-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-34.60-lowlatency 3.13.11.4 Uname: Linux 3.13.0-34-lowlatency i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CurrentDesktop: Unity Date: Thu Aug 28 04:01:16 2014 ExecutablePath: /usr/bin/webapp-container InstallationDate: Installed on 2013-03-08 (536 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) SourcePackage: webbrowser-app UpgradeStatus: Upgraded to trusty on 2014-04-19 (130 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362314/+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 974480] Re: Notification area whitelist is obsolete
Hi, Is it possible to implement a indicator for a place for those legacy software icons? People may shut up if there's still a way to access them. -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+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
