[Touch-packages] [Bug 2023282] [NEW] The module visible providers take 1min, but the UI shows a timeout in the 30s
Public bug reported: 1.Environment Image: pc-stella-jammy-amd64-20230215-269 modem:FM350-GL-02-08 Test SIM Card: Unicom Module IMEI: 863714050025511 NetworkManager:1.36.6 2. Test Steps 1). Insert the SIM card 2). Boot into system 3). Open System Setting->Mobile Network 4). Disable Mobile Data 5). Click Network 6). Disable Automatic 3. Expected Result show visible providers success 4. Actual Result show visible providers timeout I wonder if visible providers on the UI can be adjusted to 90s? Ensure that the success of visible providers is displayed ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/2023282 Title: The module visible providers take 1min, but the UI shows a timeout in the 30s Status in network-manager package in Ubuntu: New Bug description: 1.Environment Image: pc-stella-jammy-amd64-20230215-269 modem:FM350-GL-02-08 Test SIM Card: Unicom Module IMEI: 863714050025511 NetworkManager:1.36.6 2. Test Steps 1). Insert the SIM card 2). Boot into system 3). Open System Setting->Mobile Network 4). Disable Mobile Data 5). Click Network 6). Disable Automatic 3. Expected Result show visible providers success 4. Actual Result show visible providers timeout I wonder if visible providers on the UI can be adjusted to 90s? Ensure that the success of visible providers is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2023282/+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 1877450] Re: Executing "sudo apport-bug /var/crash/some-path.crash" leads to "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13] Permission denied" very often
My feeling is that this is due to the fact that the owner of the file is not root. I have the same problem. In my case, it was the `kernoops` who owns the `linux-image-5.15.0-67-generic.33564.crash` file, which is why `apport-cli` (or `apport-bug` in your case) cannot modify updating the file. After manually `chown` the file to root, I no longer have the problem. It is just weird that the apport didn't consider situations like these. In your case, it is the `mate` who owns the crash file. -- 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/1877450 Title: Executing "sudo apport-bug /var/crash/some-path.crash" leads to "ERROR: Cannot update /var/crash/some-path.crash: [Errno 13] Permission denied" very often Status in apport package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Get some crash file of crashed application (in my example it was /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash ) 3. Try to send this crash file to launchpad using `sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash` Expected results: * apport opened window about sending the crash report and then opened Firefox allowing user to login to Launchoad and then to fill some details about the bug-report Actual results: * apport opened window about sending the crash, but Firefox is not opened; instead shows the error in the terminal ``` $ sudo apport-bug /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash [sudo] password for mate: ERROR: Cannot update /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash: [Errno 13] Permission denied: '/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash' ``` Note: what is interesting in this case the upload was successful: ``` $ ls -alt /var/crash/ total 5252 -rw--- 1 whoopsie whoopsie 37 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.uploaded drwxrwsrwt 2 root whoopsie4096 May 7 23:19 . -rw-r--r-- 1 root whoopsie 0 May 7 23:19 _usr_lib_mate-panel_clock-applet.1000.upload -rw-r- 1 mate whoopsie 5364223 May 7 23:12 _usr_lib_mate-panel_clock-applet.1000.crash drwxr-xr-x 14 root root4096 Apr 23 10:48 .. ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportLog: ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: called for pid 2659, signal 11, core limit 0, dump mode 1 ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: executable: /usr/lib/mate-panel/clock-applet (command line "/usr/lib/mate-panel/clock-applet") ERROR: apport (pid 2675) Thu May 7 23:10:51 2020: debug: session gdbus call: (true,) ERROR: apport (pid 2675) Thu May 7 23:10:54 2020: wrote report /var/crash/_usr_lib_mate-panel_clock-applet.1000.crash ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashReports: 600:121:127:37:2020-05-07 23:19:38.692947366 +0300:2020-05-07 23:11:44.888143341 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.uploaded 644:0:127:0:2020-05-07 23:19:37.976589335 +0300:2020-05-07 23:19:37.976589335 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.upload 640:1000:127:5364223:2020-05-07 23:12:22.348865032 +0300:2020-05-07 23:19:44.571885615 +0300:/var/crash/_usr_lib_mate-panel_clock-applet.1000.crash CurrentDesktop: MATE Date: Thu May 7 23:20:20 2020 InstallationDate: Installed on 2020-04-23 (14 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1877450/+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 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
I have been using a SUPVAN label maker https://us.supvan.com/ for two years. We were buying blank labels from China and custom-made ink cartridges. The prices were increasing so we looked to source other choices. I am in Canada and do eBay business. We need to print many shipping labels at home every day. Does anybody have any recommendations? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Invalid Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+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 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete
I have been using a SUPVAN label maker https://us.supvan.com/ for two years. We were buying blank labels from China and custom-made ink cartridges. The prices were increasing so we looked to source other choices. I am in Canada and do eBay business. We need to print many shipping labels at home every day. Does anybody have any recommendations? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/322210 Title: [needs-packaging] PPD for Dymo LabelWriter 400 not complete Status in cups package in Ubuntu: Invalid Bug description: Binary package hint: cups Release: 8.10 Cups package version: 1.3.9-2ubuntu6.1 I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354. I chose the only available driver: Dymo Label Printer, 1.3 Problem: I could not set the correct label size as the Multi-Purpose labels are missing from the ppd-file. The result is that I get printouts which do not fit the labels. Solution: I downloaded the driver from the manufacturer and extracted the lines for the Multi-Purpose labels from their ppd-file. drivers page: https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101 driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz What should be done is that the ppd-file in cups should be updated with all the labels in the manufacturers ppd. Depending on their license. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/322210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Wed, Feb 8, 2023 at 10:25 AM Gunnar Hjalmarsson <1887...@bugs.launchpad.net> wrote: > > That looks like a better solution indeed, and I think I have got enough > of evidence that we should go for Sebastian's suggestion. > > ( Why didn't you mention that upstream discussion in your bug? ;) ) That should be my negligence. I only gave a link for reference from discourse.gnome.org to bugs.launchpad.net [1] but did not provide the opposite link on bugs.launchpad.net pointing to discourse.gnome.org, at that moment. > Thanks for your persistence! I'll make that change soon. OK. > ** Changed in: gdm3 (Ubuntu) >Status: Incomplete => In Progress > > ** Changed in: lightdm (Ubuntu) >Status: Incomplete => In Progress [1] https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/11?u=hongyi-zhao [2] https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2005135 Regards, Zhao > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > In Progress > Status in lightdm package in Ubuntu: > In Progress > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions > -- 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/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: In Progress Status in lightdm package in Ubuntu: In Progress Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Wed, Feb 8, 2023 at 9:15 AM Gunnar Hjalmarsson <1887...@bugs.launchpad.net> wrote: > > @Hongyi Zhao: As you wrote in the duplicate bug, my simplistic code in > comment #2, which only escapes the '<' character, would not be > sufficient. At the same time the issue I mentioned, about --no-markup > making \n being displayed literally instead of interpreted as a newline, > still stands. > > Probably this variant would do it: > > TEXT=$(printf '%s' "$TEXT" | sed 's/&/\/g; > s/ s/>/\/g; > s/"/\/g; > s/'"'"'/\/g') > > But before making the change, I would appreciate some feedback from you > or others that that addition to /etc/gdm3/config-error-dialog.sh would > address the issues you have observed. Please see the comments given by Sebastian Keller here [1]. [1] https://discourse.gnome.org/t/are-you-sure-you-want-to-proceed-message-on-login/13758/13 Best, Zhao > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > Incomplete > Status in lightdm package in Ubuntu: > Incomplete > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions > -- 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/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+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 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature
The following paragraphs are copied from the [issue comment](https://github.com/ibus/ibus/issues/2271#issuecomment-1421247325). I have the same problem in Ubuntu 20.04.5 LTS. I didn't have this problem until recently (one month). I am a Chinese speaker and use `ibus-libpinyin`. I am not a Google Chrome user. Instead, I encounter this problem in Firefox, Gnome Terminal, Anki, and everywhere. And very often, this problem is not consistent for me. It occurs consistently for a short period (5 minutes). And after a while, it goes away by itself. In addition to `gnome-terminal-server has no capability of surrounding- text feature`, I also have the accompanying `../clutter/clutter/clutter- actor.c:10558: clutter_actor_set_allocation() function can only be called from within the implementation of the ClutterActor::allocate() virtual function` message. The suurounding-text message only occurs when I switch IME in terminal, but the clutter actor message occurs every time I swich IME anywhere. Oops, I also got `firefox has no capability of surrounding-text feature` message in the output of `journalctl -xe`. -- 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/1900640 Title: Ubuntu 20.04 has no capability of surrounding-text feature Status in ibus: Unknown Status in ibus package in Ubuntu: Invalid Bug description: I recently upgrade my Ubuntu LTS from 18.04 to 20.04. After the upgrade, I failed to type Thai text with any combining character in some apps. The log contains this error message: `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 09:07:10.843: google-chrome-stable has no capability of surrounding-text feature` `gnome-terminal-[2589]: gnome-terminal-server has no capability of surrounding-text feature` Expected behavior: Capable of typing any Thai character in any app. Actual behavior: Only few apps support typing Thai character, e.g. Firefox, Gnome Text Editor. Step to reproduce: 1. Boot up the machine. 2. Open Google Chrome. 3. Switch keyboard layout to `Thai (LibThai)` 4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with Thai keyboard layout. Current workaround: Whenever you want to type Thai switch 1. Open `Gnome Text Editor` 2. Switch keyboard layout to `Thai (LibThai)` 3. Switch to Chrome 4. Type Thai To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1900640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1887252] Re: config-error-dialog.sh should pass --no-markup
On Tue, Feb 7, 2023 at 10:45 AM Daniel van Vugt <1887...@bugs.launchpad.net> wrote: > > ** Tags added: jammy lunar > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2005135). > https://bugs.launchpad.net/bugs/1887252 > > Title: > config-error-dialog.sh should pass --no-markup > > Status in gdm3 package in Ubuntu: > Incomplete > Status in lightdm package in Ubuntu: > Incomplete > > Bug description: > I modified my ~/.profile to call "logger". This resulted in in > producing some output on stderr like > > ``` > <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... > ``` > > This showed an empty zenity prompt. > > Logs suggest zenity was failing because it was treating `<13>` as > pango markup. > > ``` >from markup due to error parsing markup: Error on line 3 char 6: “13” is > not a valid > ``` > > We should not assume the error message strings contain valid markup, > since their source is unknown. So, what should be the appropriate bug fix method in this scenario? > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+subscriptions Best, Zhao -- 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/1887252 Title: config-error-dialog.sh should pass --no-markup Status in gdm3 package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: I modified my ~/.profile to call "logger". This resulted in in producing some output on stderr like ``` <13>Jul 11 13:02:46 /usr/sbin/lightdm-session[1408]: profile sourced ... ``` This showed an empty zenity prompt. Logs suggest zenity was failing because it was treating `<13>` as pango markup. ``` from markup due to error parsing markup: Error on line 3 char 6: “13” is not a valid ``` We should not assume the error message strings contain valid markup, since their source is unknown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1887252/+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 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
For my case, I simply cannot update the systemd to solve this problem since the address I want to bind belongs to virtual tunnel device which only gets added when there is a new tunnel connection. Oops! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] dnsmasq will fail to respond on network devices that weren't up when its service started, thus not binding as expected. [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] Straightforward packaging fix to the service to make it delay startup until after the network is online. https://bugs.debian.org/cgi- bin/bugreport.cgi?att=1;bug=774970;filename=774970-network- online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+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 1316873] Re: Left mouse button stops working
The mouse works well on 12.04. After upgrade to 14.04, it start to have this same problem. It still exist after upgrade to 16.04. -- 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/1316873 Title: Left mouse button stops working Status in xorg package in Ubuntu: Confirmed Bug description: This problem has plagued me for a few years across different laptops and Ubuntu versions. Current I am experiencing this on a Dell Inspiron 15z running Ubuntu 14.04 LTS. It typically starts after I have used the chat or call feature in gmail, by clicking on the phone icon in the left chat margin. I am a Firefox user and have not tested this with chrome etc. It has not happened if i dont install google-talkplugin so it is quite possible that the plugin is to blame. Symptom === The left mouse button on all attached mice - USB , Trackpad and touch - will not do anything however the right mouse button continues to work. This happens to all applications and also to the desktop. The keyboard continues to function as normal. When this occurs , my solution is to Alt-F4 close all windows and log out of the X session. When I re-login the left mouse button works as normal. This is an irritant and work disruptor as I have to save all browser and desktop applications to safe state before I logout to reset the mouse. I will appreciate any soltion or workaround. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 6 21:41:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:058f] InstallationDate: Installed on 2014-04-17 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 5523 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0GKGJG dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5523 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 6 21:20:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5558 vendor CMN xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
ibus-daemon eats up cpu when i use ibus-pinyin to add receiver email with thunderbird and have address autocomplete enabled. -- 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/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in ibus package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+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 1446658] Re: lxc-test-apparmor fails on aarch64
I also find the same issue in another ARM board, I can confirm that it's just following sentence to cause the failed result: run_cmd lxc-create -t download -n c1 -- -d ubuntu -r trusty -a $ARCH It will try to check the following file and download a image from website indexed in this file, if success, then create a container. http://images.linuxcontainers.org//meta/1.0/index-user Because the parameter $ARCH is arm64 definitely, and I can't find any index with arm64 in above file and any arm64 directory in following position yet. http://images.linuxcontainers.org/images/ubuntu/vivid/ I guess this is just the root case of this issue. I also find the similar sentence in following file, and all these test cases will fail on ARM board too, I think this is their common root cause. lxc-test-apparmor-mount lxc-test-usernic lxc-test-autostart lxc-test-usernic.in Beside this, I also found there are so many hard-code about trusty in multi lxc-tests cases listed as follows: justin@D02-VIVID:~/lxc/lxc-1.1.2/src/tests$ grep -R 'trusty' . ./lxc-test-apparmor-mount:run_cmd lxc-create -t download -n $cname -- -d ubuntu -r trusty -a $ARCH Binary file ./get_item.o matches ./lxc-test-usernic.in:run_cmd lxc-create -t download -n b1 -- -d ubuntu -r trusty -a $ARCH ./lxc-test-autostart:lxc-create -t download -n $CONTAINER_NAME -- -d ubuntu -r trusty -a $ARCH ./lxc-test-usernic:run_cmd lxc-create -t download -n b1 -- -d ubuntu -r trusty -a $ARCH Binary file ./lxc-test-get_item matches Binary file ./lxc-test-createtest matches ./lxc-test-unpriv:run_cmd lxc-create -t download -n c1 -- -d ubuntu -r trusty -a $ARCH I'm afraid that if this will cause that these test cases can't be compatible to different Ubuntu distribution? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1446658 Title: lxc-test-apparmor fails on aarch64 Status in apparmor package in Ubuntu: New Bug description: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 DistroRelease: Ubuntu 14.04 KernLog: Package: lxc 1.0.7-0ubuntu0.1 PackageArchitecture: arm64 ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Tags: trusty uec-images Uname: Linux 3.19.2 aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirtd _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1446658/+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 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
Affects me too. Google Chrome, Image Viewer, GVim, Gnome Terminal are all very slow. Switching workspace to the above applications are very slow as well. However, playing Team Fortress 2 on Steam works perfectly. I am using System76 15.6 Gazelle Professional laptop with Intel High Definition Graphics 4600. Ubuntu Gnome 14.10 upgraded from 14.04 -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible chops (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway. Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+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 1383297] Re: Edge intro/demo redesign
It is very important to explain the differences between short and long swipes from the right edge in the tutorial. From our beta testing user research, after three week's use of the phone, participants still did not understand the distinctions between these two gestures. An example comment from one of the participants: I can never manage to bring out the page where has all the apps that I could close, every time when I got it, only accidentally -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1383297 Title: Edge intro/demo redesign Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Triaged Bug description: A while ago, Design gave me new visuals for the edge demo [1], but it kept getting put off for other work. I'm filing a bug here to help it not get forgotten and so it can be assigned a priority. [1] https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+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
