[Bug 1835863] Re: Screens do not stay off when blanking
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835863] Re: Screens do not stay off when blanking
Why is this still marked incomplete? What other info is necessary? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835863] Re: Screens do not stay off when blanking
I'd point my finger a the amdgpu driver in that case. Unplugging the monitor in question did the trick (allowed system to blank properly). The cable is definitely good & the connection ports on both ends should be fine. This particular system is dual booted into Windows 10 where this is a non-issue. The keyboard has always been wonky (frequently it doesn't get initialized and has to be unplugged and plugged in again). I left it plugged in to run the test & the system was not adversely affected. The same amdgpu is plugged into two monitors: [1] monitor with issue (straight HDMI <> HDMI) FreeSync compatible [2] monitor that works fine (DP on gpu converted to HDMI) non-Free-Sync -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1835863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835863] Re: Screens do not stay off when blanking
Thanks for the quick reply. Here ya go. ** Attachment added: "curjournal.txt" https://bugs.launchpad.net/ubuntu/+bug/1835863/+attachment/5275982/+files/curjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1835863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835863] [NEW] Screens do not stay off when blanking
Public bug reported: After some idle period (5-15 minutes) the screens are supposed to blank and power off. They appear to do this once but then come right back on and stay on. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 9 00:09:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.0.0-19-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.0.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:67b0] (rev 80) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon R9 390X [1043:04df] InstallationDate: Installed on 2019-06-21 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=df9fe4e8-eacc-47f5-9df4-85a524802645 ro quiet splash radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2704 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2704:bd02/18/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97I-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835863 Title: Screens do not stay off when blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1835863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743183] Re: Mouse left button not being noticed when clicked under Wayland - works under x11
*** This bug is a duplicate of bug 1747568 *** https://bugs.launchpad.net/bugs/1747568 So.. I marked it as a duplicate of the bug you mentioned. Still.. invalid really doesn't seem appropriate. The description says: Invalid: Not a bug. May be a support request or spam. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743183 Title: Mouse left button not being noticed when clicked under Wayland - works under x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743183] Re: Mouse left button not being noticed when clicked under Wayland - works under x11
*** This bug is a duplicate of bug 1747568 *** https://bugs.launchpad.net/bugs/1747568 Well... It doesn't sound like it's fixed & certainly not invalid. If it still doesn't work when using updated versions of packages available in those PPA's, it's not really fixed. Is there a way to mark it as duplicate instead? ** This bug has been marked a duplicate of bug 1747568 Mouse clicks ignored in Wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743183 Title: Mouse left button not being noticed when clicked under Wayland - works under x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743183] Re: Mouse left button not being noticed when clicked under Wayland - works under x11
** Changed in: gnome-shell (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743183 Title: Mouse left button not being noticed when clicked under Wayland - works under x11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM
Yeah 'guest' for me means VM running on a host. That VM system is unable to start so I wouldn't be able to gather or report anything from there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM
I'm not sure but can try. The issue is that the system freezes when trying to start the VM at all so it doesn't get far enough. Are you sure you don't mean to install the -evdev package in the host? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749895] Re: Mouse & Keyboard completely unresponsive when starting a VM
:~$ virt-manager --version 1.4.0 ** Attachment added: "about virt-manage" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+attachment/5057545/+files/virt-manager-about.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749895] [NEW] Mouse & Keyboard completely unresponsive when starting a VM
Public bug reported: Could be virt-manager or gnome-shell related. I was passing through 1 USB device that wasn't my main mouse or keyboard. Otherwise pretty normal configuration that I've used before. After the VM's bios screen, the whole system froze except the clock in the desktop menu bar/panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 Uname: Linux 4.15.1-041501-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 23:47:02 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-27 (112 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749895 Title: Mouse & Keyboard completely unresponsive when starting a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748346] Re: Desktop Environment (GNOME) Freezes on Login
** Description changed: I can't log in anymore. I've force rebooted several times. Was working fine with occasional freezes until recently but now it freezes every login. 17.10 - Wayland was disabled as per: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568 (system info & bug details are the same as that report) Mouse usually just stays frozen in the middle of the Ubuntu Purple screen. Sometimes the user desktop would partially load but the mouse would still be frozen in the middle. + + No keyboard keys work either but keyboard does have power. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748346 Title: Desktop Environment (GNOME) Freezes on Login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1748346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
@tkr Np - it really smoothed things over for me too. In terms of oibaf PPA, I am also pretty sure that mouse stuff was working for quite a while after initially setting up the PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
@tkr Same fix for me but I am using: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers Hovering also was ignored for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
GSettingsChanges: org.gnome.shell enabled-extensions ['temperature@xtranophilist', 'openweather-extens...@jenslody.de', 'screenshot-window-si...@gnome-shell-extensions.gcampax.github.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'show...@kyle.aims.ac.za', 'steal-my-fo...@kagesenshi.org', 'shell-volume-mi...@derhofbauer.at', 'audio-output-switcher@anduchs', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'apps-m...@gnome-shell-extensions.gcampax.github.com', 'places-m...@gnome-shell-extensions.gcampax.github.com', 'window-l...@gnome-shell-extensions.gcampax.github.com', 'appindicatorsupp...@rgcjonas.gmail.com', 'freon@UshakovVasilii_Github.yahoo.com', 'caffe...@patapon.info', 'gnome-shell-screens...@ttll.de'] org.gnome.shell command-history ['r'] org.gnome.shell remember-mount-password true org.gnome.shell had-bluetooth-devices-setup true org.gnome.desktop.interface cursor-theme 'whiteglass' org.gnome.desktop.interface clock-show-seconds true org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' org.gnome.desktop.interface icon-theme 'Adwaita' org.gnome.desktop.interface clock-format '12h' org.gnome.desktop.interface gtk-theme 'Arc-Dark' org.gnome.desktop.interface clock-show-date true org.gnome.desktop.interface document-font-name 'Ubuntu 10' ** Attachment removed: "GsettingsChanges.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+attachment/5049501/+files/GsettingsChanges.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+attachment/5049502/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
** Attachment added: "Journal Errors" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+attachment/5049824/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049502/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049503/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049501/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] Re: Mouse clicks ignored in Wayland
apport information ** Tags added: apport-collected artful third-party-packages ** Description changed: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-10-27 (102 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + Tags: artful third-party-packages + Uname: Linux 4.15.0-041500rc9-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip emby libvirt lpadmin plex plugdev sambashare sudo users video + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1747568/+attachment/5049500/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747568] [NEW] Mouse clicks ignored in Wayland
Public bug reported: If I disable Wayland, mouse clicks start working again. Randomly started occurring sometime after initial install. Ubuntu 17.10 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747568 Title: Mouse clicks ignored in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1747568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
Here it is: https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1747568 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
If you can instruct me on how to gather the pertinent information, I can make a report. Honestly though, it seems like the chances of some unique rare issue that few have is going to get much attention. If it comes to it that I need Wayland on this system, I'd sooner just reinstall which typically resets weird elusive configuration issues of which there could be many. It's too bad there isn't a financially backed bounty system somewhere for fixing bugs? I might pay into some reward to fix these odd issues that aren't likely to get much attention. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730174] Re: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop
Ehh... Not really worth the trouble at this point as I've resolved it myself by just disabling Wayland. Since Wayland won't be default in 18.04 anyway, there's a good chance the issue will be fixed by 18.10. I've posted the same solution on an Ask Ubuntu question so it may help others. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] mouse clicks are completely ignored both in Gnome's gdm and once logged in to the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730174] Re: [artful] Mouse broken after upgrade from 17.04 to 17.10
This resolved the issue for me: https://askubuntu.com/a/968265/89202 "If you wish to do it permanently, edit /etc/gdm3/custom.conf and uncomment the line #WaylandEnable=false by removing the # in front. Save the file and then on reboot you will never see the cog asking for which session to use." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] Mouse broken after upgrade from 17.04 to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730174] Re: [artful] Mouse broken after upgrade from 17.04 to 17.10
Same issue... Still broken. X.org works - Wayland doesn't let you click on anything. This includes the login screen. Running kernel 14.5-rc7. sudo ubuntu-drivers autoinstall did nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730174 Title: [artful] Mouse broken after upgrade from 17.04 to 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300215] Re: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory
This is still broken in Ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300215 Title: Failed to open VDPAU backend libvdpau_i965.so: cannot open shared object file: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvdpau/+bug/1300215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1069133] Re: Get upgrade error 12.04 - 12.10 "Could not determine upgrade" - xorg from ppa
Damn... how many duplicates have to get created before this gets fixed... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1069133 Title: Get upgrade error 12.04 - 12.10 "Could not determine upgrade" - xorg from ppa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1069133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711029] Re: Fails to upgrade from 16.04 to 17.04
*** This bug is a duplicate of bug 1069133 *** https://bugs.launchpad.net/bugs/1069133 Damn... How many duplicates have to get created before this issue gets fixed... It's not just that the do-release-upgrade should automatically handle what is needed to be done - it also fails even after I manually purge and remove the PPA with python3 requirements. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711029 Title: Fails to upgrade from 16.04 to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1711029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711029] [NEW] Fails to upgrade from 16.04 to 17.04
Public bug reported: do-release-upgrade fails to upgrade from 16.04 to 17.04 - no information/error given as to why. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.22 ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76 Uname: Linux 4.4.0-92-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Aug 16 00:27:35 2017 InstallationDate: Installed on 2017-05-18 (90 days ago) InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.8) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2017-08-16 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2017-08-16T00:23:14.442123 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711029 Title: Fails to upgrade from 16.04 to 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1711029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691924] Re: do-release-upgrade fails
Huh? What's this about? There should be enough info in the logs to confirm this. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691924 Title: do-release-upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691924] Re: do-release-upgrade fails
I did see that unhelpful generic boiler plate message every time I tried to run `sudo do-release-upgrade` yes. That doesn't exactly constitute a helpful error message. It's more like saying, "There's a problem and what you tried to do failed" which I already knew by the process not succeeding. What that process response should have said is that I needed to uninstall xserver-xorg-video-all because it was causing the upgrade to fail. All the PPA's I have are listed in: https://launchpadlibrarian.net/320297430/VarLogDistupgradeMainlog.txt Take a look at https://launchpadlibrarian.net/320297428/VarLogDistupgradeAptlog.txt which claims, presumably incorrectly, that tons of packages are 'Broken'. There's also a handful other automatically attached logs/system info on this bug. To it's credit (do-release-upgrade), it did print a line with a `ubuntu-bug ...` command that automatically generated this report. That's pretty awesome. All of this is attached to this report: Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8") JournalErrors.txt Edit (146.2 KiB, text/plain; charset="utf-8") VarLogDistupgradeAptclonesystemstate.tar.gz Edit (814.2 KiB, application/x-gzip) VarLogDistupgradeAptlog.txt Edit (49.8 KiB, text/plain; charset="utf-8") VarLogDistupgradeLspcitxt.txt Edit (3.4 KiB, text/plain; charset="utf-8") VarLogDistupgradeMainlog.txt Edit (14.7 KiB, text/plain; charset="utf-8") VarLogDistupgradeScreenlog.txt Edit (1.0 MiB, text/plain; charset="utf-8") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691924 Title: do-release-upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691924] Re: do-release-upgrade fails
Turned out that the culprit, despite a very long list of Broken packages in Apt.log, was this inconspicuous line in Main.log: DEBUG Installing 'xserver-xorg-video-all' (Distro KeepInstalledPkgs rule) So while technically my issue with this is fixed I think some work needs to be done to provide better, more accurate output with regards to issues like this. Same problem can manifest for different users with different packages being problematic and the Apt.log list of Broken packages in my case actually included essential packages to my ubuntu-gnome-desktop bundle which would have ravaged my system had I blindly removed them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691924 Title: do-release-upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691924] [NEW] do-release-upgrade fails
Public bug reported: I originally installed Kubuntu 16.04 but since upgraded to 16.10 and switched over to Ubuntu GNOME (ubuntu-gnome-desktop). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 Uname: Linux 4.11.1-041101-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Thu May 18 23:38:33 2017 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-05-19 (0 days ago) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade yakkety ** Description changed: I originally installed Kubuntu 16.04 but since upgraded to 16.10 and - switch over to Ubuntu-GNOME (ubuntu-gnome-desktop) + switched over to Ubuntu GNOME (ubuntu-gnome-desktop). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 Uname: Linux 4.11.1-041101-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Thu May 18 23:38:33 2017 PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-05-19 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691924 Title: do-release-upgrade fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1691924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1095086] Re: When connecting to a server i get "Unable to find matching CELT codecs with other clients. You will not be able to talk to all users."
For me the issue was that I was launching mumble via a .desktop that pointed to a sym link I placed in /usr/bin pointing to ~/mumble/release/mumble. If I launched mumble manually through it's release directory, I didn't get this warning. To fix this I added `CONFIG+=no-bundled-celt` to the qmake line and installed libcelt packages and it's working now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1095086 Title: When connecting to a server i get "Unable to find matching CELT codecs with other clients. You will not be able to talk to all users." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mumble/+bug/1095086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1262201] Re: System freezes after suspend session
Still an issue with Nvidia 660 Ti running propriety drivers on Ubuntu GNOME 16.04.1. Freezes within 1 minute of resuming 100% of the time (about 12/12 so far before disabling it). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1262201 Title: System freezes after suspend session To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1262201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1446655] Re: Gnome-Shell freezes/crashes after resuming from suspend
Has nothing to do with Nouveau for me. Been using proprietary Nvidia drivers from day one and 100% of suspend sessions freeze after resuming usually within a minute or less. Base system is a fresh Ubuntu GNOME 16.04.1 install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1446655 Title: Gnome-Shell freezes/crashes after resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1446655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599361] [NEW] package awn-applets-c-core 0 .4.0-0ubuntu1 failed to install/upgrade: 依 赖关系问题 - 仍未被配置
*** This bug is a duplicate of bug 512096 *** https://bugs.launchpad.net/bugs/512096 Public bug reported: pkg (子进程)：无法运行 已安装的 post-installation 脚本: 可执行文件格式错误 dpkg：处理 avant-window-navigator (--configure)时出错： 子进程 已安装的 post-installation 脚本 返回了错误号 2 dpkg：依赖关系问题使得 awn-applets-c-core 的配置工作不能继续： awn-applets-c-core 依赖于 avant-window-navigator；然而： 软件包 avant-window-navigator 还没有被配置。 dpkg：处理 awn-applets-c-core (--configure)时出错： 依赖关系问题 - 仍未被配置 正在设置 python-awn-extras (0.4.0-0ubuntu1) ... dpkg (子进程)：无法运行 已安装的 post-installation 脚本: 可执行文件格式错误 dpkg：处理 python-awn-extras (--configure)时出错： 子进程 已安装的 post-installation 脚本 返回了错误号 2 dpkg：依赖关系问题使得 awn-applets-python-core 的配置工作不能继续： awn-applets-python-core 依赖于 avant-window-navigator；然而： 软件包 avant-window-navigator 还没有被配置。 awn-applets-python-core 依赖于 python-awn-extras (= 0.3.9~bzr1944)；然而： 软件包 python-awn-extras 还没有被配置。 dpkg：处理 awn-applets-python-core (--configure)时出错： 依赖关系问题 - 仍未被配置 No apport report written because MaxReports is reached already 在处理时有错误发生： avant-window-navigator awn-applets-c-core python-awn-extras awn-applets-python-core 正在设置 avant-window-navigator (0.4.0-0ubuntu1) ... dpkg (子进程)：无法运行 已安装的 post-installation 脚本: 可执行文件格式错误 dpkg：处理 avant-window-navigator (--configure)时出错： 子进程 已安装的 post-installation 脚本 返回了错误号 2 正在设置 python-awn-extras (0.4.0-0ubuntu1) ... dpkg (子进程)：无法运行 已安装的 post-installation 脚本: 可执行文件格式错误 dpkg：处理 python-awn-extras (--configure)时出错： 子进程 已安装的 post-installation 脚本 返回了错误号 2 dpkg：依赖关系问题使得 awn-applets-c-core 的配置工作不能继续： awn-applets-c-core 依赖于 avant-window-navigator；然而： 软件包 avant-window-navigator 还没有被配置。 dpkg：处理 awn-applets-c-core (--configure)时出错： 依赖关系问题 - 仍未被配置 dpkg：依赖关系问题使得 awn-applets-python-core 的配置工作不能继续： awn-applets-python-core 依赖于 avant-window-navigator；然而： 软件包 avant-window-navigator 还没有被配置。 awn-applets-python-core 依赖于 python-awn-extras (= 0.3.9~bzr1944)；然而： 软件包 python-awn-extras 还没有被配置。 dpkg：处理 awn-applets-python-core (--configure)时出错： 依赖关系问题 - 仍未被配置 ProblemType: Package DistroRelease: Ubuntu 10.04 Package: awn-applets-c-core 0.4.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Jun 28 21:33:13 2010 ErrorMessage: 依赖关系问题 - 仍未被配置 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: awn-extras-applets Title: package awn-applets-c-core 0.4.0-0ubuntu1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 ** Affects: awn-extras-applets (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- package awn-applets-c-core 0.4.0-0ubuntu1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 https://bugs.launchpad.net/bugs/599361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 599361] Re: package awn-applets-c-core 0.4 .0-0ubuntu1 failed to install/upgrade: 依 赖关系问题 - 仍未被配置
*** This bug is a duplicate of bug 512096 *** https://bugs.launchpad.net/bugs/512096 ** Attachment added: AptOrdering.txt http://launchpadlibrarian.net/51033877/AptOrdering.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/51033878/Dependencies.txt ** Attachment added: Df.txt http://launchpadlibrarian.net/51033879/Df.txt ** Attachment added: Dmesg.txt http://launchpadlibrarian.net/51033880/Dmesg.txt ** Attachment added: DpkgTerminalLog.txt http://launchpadlibrarian.net/51033881/DpkgTerminalLog.txt -- package awn-applets-c-core 0.4.0-0ubuntu1 failed to install/upgrade: 依赖关系问题 - 仍未被配置 https://bugs.launchpad.net/bugs/599361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417085] Re: want more features for Writer user dictionaries
Um, it's me again. Just ran out of space in one of my several medical dictionaries Maybe there's another way to approach the problem? (LARGE list of user words to spellcheck.) -- want more features for Writer user dictionaries https://bugs.launchpad.net/bugs/417085 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 133056] Re: [upstream] adding word to dictionary should not ask for dictionary file
Interesting thread. I found it because I'm needing _more_ custom dictionary options. Until recently, I was only a casual word processor user, but have been using multiple user dictionaries for many years. I figured that if I was going to modify (add to) the dictionary(s), I should learn how to use them. Maybe I'm the odd man out? -- [upstream] adding word to dictionary should not ask for dictionary file https://bugs.launchpad.net/bugs/133056 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417085] [NEW] want more features for Writer user dictionaries
Public bug reported: Binary package hint: openoffice.org I'm working as a English-language editor/proofreader for a small writer/publisher of reference books AND for the English-language- instruction faculty of a major university - in a country where English is broadly, but very poorly, known. Due to its eclectic nature, my word processing benefits greatly from extensive use of custom dictionaries. It would benefit even more from the following 4 advanced features, should you be able to incorporate them: A. Associating a document with specific dictionaries , like my old WordPerfect did, would eliminate the need for me to switch dictionary _sets_ when I look at a document on a different topic: perhaps a choice between Use Associated and Use Open dictionaries, and Don't Ask Again. B. Enabling of multi-word entries As an example, loa loa has come up a number of times. I don't want loa in my dictionary because as a single word it is meaningless, but it is a misspelling for many common words such as low, load, loaf, Lola. C. Checking for typeface (specifically, italics) The Chicago Manual of Style (which we follow) specifies that Latin botanical names always be italicized. An arachnid (regular font) is a kind of bug, but Anachnida (italicized) is their official botanical Class, and Araneae (italicized) is the Order spiders belong to. This similarity between English common names and official Latin identifiers is extremely commonly seen in infectious diseases. Again, an Apply font restrictions toggle may be an idyllic way to go. D. Creating/applying rules May of the words I add are used in multiple forms. Most may have the first letter capitalized or not, for starters. Nouns have plural and possessive forms, verbs have tense. Often words may form nouns, verbs, adjectives, and/or adverbs. That's a lot of entries for one word. For starters, a dialog box with Capitalize: Always/Never/Both, Forms plurals, Forms Possessive, and Is Regular Verb would be a big help. (I'd be happy to hex edit additional rules.) You may decide to divide into traditional and rule set dictionaries. Um, I'm a newbie to Linux bug reporting. Is this message in the right spot? Too verbose? I have a document with a little more detail, if it's of any use. It seemed too verbose to post here. ProblemType: Bug Architecture: i386 Date: Fri Aug 21 20:14:30 2009 DistroRelease: Ubuntu 8.04 Package: openoffice.org-core 1:2.4.1-1ubuntu2.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/lib/openoffice/program:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.24-24-generic i686 ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug -- want more features for Writer user dictionaries https://bugs.launchpad.net/bugs/417085 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 417085] Re: want more features for Writer user dictionaries
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/30647645/Dependencies.txt -- want more features for Writer user dictionaries https://bugs.launchpad.net/bugs/417085 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 55959] Re: Cirrus Logic CL5446 Video card not supported/working in 6.06 Live
Please feel free to do whatever you like. I gave up on Unbunto when there was no interest in anyone fixing this issue, which PREVENTED me using Ubuntu. I exclsuively use Compaq hardware, and this device is the built-in Video supported by Compaq Diagnostics. By nobody addressing this issue, it actually saved me a LOT of issues down the track. The zero response showed me EXACTLY what the support for Ubuntu was like, and so enable me to avoid choosing Ubuntu, only to find out there was no support AFTER I had invested a lot of my time setting up Ubuntu on my hardware. FYI, I also reported a problem with the same release of Ubuntu that prevented access to the Compaq Hadware Diagnostics Partition (To find it, seach for F10 Compaq 1600). So, I encountered a problem problem that prevented me SEEING the Ubunto screen output, and I could no longer use the Verdor-supplied Hardware diagnostics. And in BOTH issues, there was NO response for Weeks or Months. Tell me ANYONE who would use an operating System with issues like that, when nobody showed even the slightest interest in even a Triage of the issues in (say) the first 2 weeks after the problem was reported. - Please don't feel bad, because I don't. But, please also don't think that there is anything approaching even a semi-professional level of support for Ubuntu. If there was an appropriate level of Supportm then there would be NO open issues THIS old. And this will ultimately limit the number and type of people who install Ubuntu. And, please don't give me a bleeding heart story about everybody working for free. All that was required was a quick assessment of the situation, and an update. It could have been as simple as: We are sorry that this issue is preventing you using Ubuntu. We have never had anyone else report this problem, so it would appear that you are the only person in the world affected in this manner. We have other issues that have the potential to affect many more Ubuntu users, so we hope you will understand that we might not be able to do any further investigation in the forseeable future. We have closed this issue with a status of 'UNDIAGNOSED, and we hope that you will understand why we have to concentrate on more mainstream issues affecting a larger number people. - There is no need to respond to this email message. Regards, Wesley. -- Wesley Summers Voice: +613 9857 4258 Mobile: +614 14 866 705 18 Singleton Road, Balwyn North 3104 Gareth Fitzworthington [EMAIL PROTECTED] wrote: = This bug has had no activity for a considerable period. This is a check to see if there is still interest in investigating this bug report. ** Changed in: linux-source-2.6.15 (Ubuntu) Status: New = Incomplete -- Cirrus Logic CL5446 Video card not supported/working in 6.06 Live https://bugs.launchpad.net/bugs/55959 You received this bug notification because you are a direct subscriber of the bug. -- Cirrus Logic CL5446 Video card not supported/working in 6.06 Live https://bugs.launchpad.net/bugs/55959 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 55961] Re: Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key
I never said it was in the MBR. This issue was reported a LONG time ago. I reported it, expecting more interest and a faster response, and offered my assistance to get it resolved. Obviously, my expectations were not met, and I have abandoned any plans of using Ubuntu. So, please don't ask for my assistance again. Wesley. == Ante Karamatić [EMAIL PROTECTED] wrote: Enigma-TS wrote: Regardless of what you might think, Windows does NOT 'erase' the F10 'feature' of the Compaq system. Then it isn't in MBR or you where using modified Windows installation (default Windows installation formats MBR of disk)? Could you find out type of partition on which those tools are located? -- Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key https://bugs.launchpad.net/bugs/55961 You received this bug notification because you are a direct subscriber of the bug. -- Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key https://bugs.launchpad.net/bugs/55961 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 55961] Re: Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key
Regardless of what you might think, Windows does NOT 'erase' the F10 'feature' of the Compaq system. Ubuntu is the only Operating system that I have experienced doing it. Regards, Wesley. Ante Karamatić [EMAIL PROTECTED] wrote: If this 'shortcut' is really in MBR, then installation of every operating system would erase it (Windows, any Linux...). Grub should detect all partitions when it is installed. Just as how it detects Windows partition, so it should detect this one. Can you tell what's the type of partition? FAT? ** Also affects: grub (Ubuntu) Importance: Undecided Status: Unconfirmed -- Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key https://bugs.launchpad.net/bugs/55961 You received this bug notification because you are a direct subscriber of the bug. -- Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key https://bugs.launchpad.net/bugs/55961 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93706] [apport] BuildIndex.exe crashed with SIGSEGV
Public bug reported: I was running an update, the update manager said that everything installed correctly, the system prompted me to reboot, then I had a dialog box that said Buildindex.exe unexpectedly crashed. It seemed to cause no issue after that. I just upgraded to Ubuntu 7.04 The feisty dawn beta last week. ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Mon Mar 19 09:08:41 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/lib/beagle/BuildIndex.exe InterpreterPath: /usr/bin/mono Package: beagle 0.2.16.3-0ubuntu2 PackageArchitecture: i386 ProcCmdline: beagle-build-index --debug /usr/lib/beagle/BuildIndex.exe --target /var/cache/beagle/indexes/documentation --disable-directories --recursive --allow-pattern *.xml,*.html,*.docbook /usr/share/doc /usr/local/share/doc /opt/kde3/share/doc /opt/gnome/share/gnome/help /usr/share/gnome/help /opt/gnome/share/gtk-doc/html /usr/share/gtk-doc/html /usr/share/gnome/html ProcCwd: / ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=en_US.UTF-8 Signal: 11 SourcePackage: beagle Stacktrace: #0 0x08140038 in ?? () StacktraceTop: ?? () ThreadStacktrace: Uname: Linux ubuntu 2.6.20-12-generic #2 SMP Sun Mar 18 03:07:14 UTC 2007 i686 GNU/Linux UserGroups: ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- [apport] BuildIndex.exe crashed with SIGSEGV https://launchpad.net/bugs/93706 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 93706] Re: [apport] BuildIndex.exe crashed with SIGSEGV
** Attachment added: CoreDump.gz http://librarian.launchpad.net/6856772/CoreDump.gz ** Attachment added: Dependencies.txt http://librarian.launchpad.net/6856773/Dependencies.txt ** Attachment added: Disassembly.txt http://librarian.launchpad.net/6856774/Disassembly.txt ** Attachment added: ProcMaps.txt http://librarian.launchpad.net/6856775/ProcMaps.txt ** Attachment added: ProcStatus.txt http://librarian.launchpad.net/6856776/ProcStatus.txt ** Attachment added: Registers.txt http://librarian.launchpad.net/6856777/Registers.txt -- [apport] BuildIndex.exe crashed with SIGSEGV https://launchpad.net/bugs/93706 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91778] Mono Crash
Public bug reported: Binary package hint: mono I'm running Ubuntu 6.10 Edgy eft and GNOME Desktop 2.16.1, both are October builds. I suddenly, without any applications running, had a pop- up dialog box stating that mono crashed. I closed the dialog box, and continued working without any problems, it seems. This is all the information I have. ** Affects: mono (Ubuntu) Importance: Undecided Status: Unconfirmed -- Mono Crash https://launchpad.net/bugs/91778 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89506] Re: Beagle crashes when creating folder on GNOME desktop
dBera wrote: Enigma, you seem to be having the problem on a regular basis. With a little effort, you may be able to provide valuable input in identifying the problem. After you login, in a terminal give, $ beagled --replace --fg This will start beagle in the terminal and print all kind of lines saying what it is doing. You can ignore them. Then create a new folder or file which you think might trigger the crash. We expect the terminal at that point to have some informative output like a stacktrace of some lines saying Exception. If you see them, please copy those lines (maybe 20 more lines before that to preserve the context) and attach it to the bug. Another user had some success by stopping the evolution-mail backend. You can give this command from a terminal, $ beagle-config daemon DenyBackend EvolutionMail restart beagle (using beagled --restart or logout/login) and see if it crashes. Thanks. Thanks. I'll try what you said, it is a weird bug. It doesn't seem to hurt anything, accept just being a slight annoyance. -- ~Rick Donahue _ When you do the right thing, most people won't notice. SeaMonkey Email Client ***Linux*** -- Beagle crashes when creating folder on GNOME desktop https://launchpad.net/bugs/89506 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89506] Re: Beagle crashes when creating folder on GNOME desktop
The enigma wrote: Cristian Aravena Romero wrote: ** Changed in: Ubuntu Sourcepackagename: None = beagle Please explain in further detail. Thanks Beagle states Beagle has to close and any work will not be saved, please report bug every once in a while. I seems to happen when I create a file or folder on the GNOME version 2.16.1, I'm running Ubuntu 6.01 the Edgy Eft, release October 2006. When I close the dialog box, there seems to be no problems after that, I can continue with what I was doing. I posted the bug on the Ubuntu site, it's number is #89506. I just wanted to get it out there, in case it becomes more of a problem. Thanks. -- ~Rick Donahue _ When you do the right thing, most people won't notice. SeaMonkey Email Client ***Linux*** -- Beagle crashes when creating folder on GNOME desktop https://launchpad.net/bugs/89506 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89506] Re: Beagle crashes when creating folder on GNOME desktop
Cristian Aravena Romero wrote: ** Changed in: Ubuntu Sourcepackagename: None = beagle Please explain in further detail. Thanks -- ~Rick Donahue _ When you do the right thing, most people won't notice. SeaMonkey Email Client ***Linux*** -- Beagle crashes when creating folder on GNOME desktop https://launchpad.net/bugs/89506 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89506] Beagle crashes when creating folder on GNOME desktop
Public bug reported: While creating a folder on the GNOME desktop version 2.16.1 on Ubuntu edgy 6.10 eft, a dialog box appears stating that Beagle has to close, you may lose any work. Closing the warning then continuing naming the folder, or whatever on the desktop seems to have no effect on the system. This happens on a stand alone machine, connected only to a high speed cable connection. The Ubuntu Linux machine is attached to a KVM switch to a Windows machine, also just connected to the high speed connection through a Cisco Linksys router. There's no wireless connection. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Beagle crashes when creating folder on GNOME desktop https://launchpad.net/bugs/89506 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55959] Cirrus Logic CL5446 Video card not supported/working in 6.06 Live
Public bug reported: Binary package hint: mkvmlinuz The Cirrus Logic CL5446 is the embedded Video hardware in one of the Compaq ProLiant 1600 models. As soon as vmlinuz is loaded, the screen goes BLANK (What I call the Black Screen Of Death - BSOD [I pronounce it: Bee Sod]). In fact, you should see a graphical screen asking you to choose a language. This same behaviour occurs on the Live, Alternate Server CDs. This is a hard error (Occurs every time). There are multiple variants of the Compaq ProLiant 1600 Model. This particular one has the'P8 BIOS, dated 11/08/2000 (Nov/08/2000). The System Configuration Utility reports an Embedded - Cirrus Logic CL5446 VGA Video Controller I also have a ProLiant 1600 with the E34 BIOS dated 04/19/2000 (Apr/19/2000). This machine's System Configuration Utility (Same version as the above machine) reports an Embedded - Cirrus Logic VGA Video Controller (NB: No 'CL5446' designation on this machine). The machine with the 'E34' BIOS does NOT exhibit this problem. The P8 E34 machines have different BIOS software, and both are patched to the Latest version. Both machines have the same amount of Memory, and SCSI RAID-5 Disk array. Both have Dual Pentium II processors (The E34 are 300MHz, while the P8 are 450MHz). The 'P8' machine has a Smart-2/P RAID Controller installed, while the 'E34' machine has a Smart-2DH RAID Controller installed. I have sufficient spare hardware to fit either controller (or matching controllers) into both machines, if that would assist in resolution of this problem. I am happy to perform additional testing, or supply further information (If requested), so that this problem can be resolved. ** Affects: mkvmlinuz (Ubuntu) Importance: Untriaged Status: Unconfirmed ** Description changed: Binary package hint: mkvmlinuz The Cirrus Logic CL5446 is the embedded Video hardware in one of the Compaq ProLiant 1600 models. - As soon as vmliuz is loaded, the screen goes BLANK (What I call the + As soon as vmlinuz is loaded, the screen goes BLANK (What I call the Black Screen Of Death - BSOD [I pronounce it: Bee Sod]). In fact, you should see a graphical screen asking you to choose a language. This same behaviour occurs on the Live, Alternate Server CDs. This is a hard error (Occurs every time). There are multiple variants of the Compaq ProLiant 1600 Model. This particular one has the'P8 BIOS, dated 11/08/2000 (Nov/08/2000). The System Configuration Utility reports an Embedded - Cirrus Logic CL5446 VGA Video Controller I also have a ProLiant 1600 with the E34 BIOS dated 04/19/2000 (Apr/19/2000). This machine's System Configuration Utility (Same version as the above machine) reports an Embedded - Cirrus Logic VGA Video Controller (NB: No 'CL5446' designation on this machine). The machine with the 'E34' BIOS does NOT exhibit this problem. The P8 E34 machines have different BIOS software, and both are patched to the Latest version. Both machines have the same amount of Memory, and SCSI RAID-5 Disk array. Both have Dual Pentium II processors (The E34 are 300MHz, while the P8 are 450MHz). The 'P8' machine has a Smart-2/P RAID Controller installed, while the 'E34' machine has a Smart-2DH RAID Controller installed. I have sufficient spare hardware to either (or matching) controller into both machines, if that would assist in resolution of this problem. I am happy to perform additional testing, or supply further information (If requested), so that this problem can be resolved. ** Description changed: Binary package hint: mkvmlinuz The Cirrus Logic CL5446 is the embedded Video hardware in one of the Compaq ProLiant 1600 models. As soon as vmlinuz is loaded, the screen goes BLANK (What I call the Black Screen Of Death - BSOD [I pronounce it: Bee Sod]). In fact, you should see a graphical screen asking you to choose a language. This same behaviour occurs on the Live, Alternate Server CDs. This is a hard error (Occurs every time). There are multiple variants of the Compaq ProLiant 1600 Model. This particular one has the'P8 BIOS, dated 11/08/2000 (Nov/08/2000). The System Configuration Utility reports an Embedded - Cirrus Logic CL5446 VGA Video Controller I also have a ProLiant 1600 with the E34 BIOS dated 04/19/2000 (Apr/19/2000). This machine's System Configuration Utility (Same version as the above machine) reports an Embedded - Cirrus Logic VGA Video Controller (NB: No 'CL5446' designation on this machine). The machine with the 'E34' BIOS does NOT exhibit this problem. The P8 E34 machines have different BIOS software, and both are patched to the Latest version. Both machines have the same amount of Memory, and SCSI RAID-5 Disk array. Both have Dual Pentium II processors (The E34 are 300MHz, while the P8 are 450MHz). The 'P8' machine has a Smart-2/P RAID
[Bug 55961] Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key
Public bug reported: Compaq ProLiant computers usually have a small Diagnostics Partition (About 50MB). This is accessed at the end of the POST. The results of the POST are cleared from the screen, and a reminder message is displayed saying that to access the Diagnostic software, you should press F10 now. This message is normally displayed for a few seconds, then if the F10 key is NOT pressed, the operating system in the active partition is loaded. Ubuntu 6.06 Live seems to intercept the F10 keypress, as controll is never passed to the Diagnostic software. The machine exhibiting this problem is a Compaq ProLiant 1600 with the P8 BIOS, that has been flashed to the 11/08/2000 (Nov/08/2000) version. This issue PREVENTS access to the software used to perform Hardware Diagnostic testing. While the configuration software can be run from CD (The Compaq SmartStart CD), the Hardware Diagnostic testing can ONLY be run from the Diagnostics Partition. As a result, the choice to use Ubuntu is NOT a choice while this issue exists - Ubuntu cannot be used if it prevents access to the Hardware Diagnostic software. I have another Compaq ProLiant 1600, but this one has the E34 BIOS dated 04/19/2000 (Apr/19/2000). I have not tried to install Ubuntu on this machine, but I could (By using additional SCSI drives for the Ubuntu software) if it was vital to the resolution of this issue. Please let me know if you require any more information. It is my intention to remove Ubuntu if this issue cannot be resolved. ** Affects: mkvmlinuz (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Ubuntu 6.06 Live prevents access to Compaq ProLiant Diagnostic Partition using F10 key https://launchpad.net/bugs/55961 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
