[Touch-packages] [Bug 1887296] Re: Moving popup windows drags the application's main window behind it
This is a feature we inherited from GNOME. It is not a design choice by Ubuntu. To disable it just set: Gnome Tweaks > Windows > Attach Modal Dialogs = OFF ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1887296 Title: Moving popup windows drags the application's main window behind it Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Boar
[Touch-packages] [Bug 1887294] Re: Display freeze
It appears you have a kernel crash in the Nvidia driver: [412515.698236] Call Trace: [412515.698244] ? _nv002628kms+0x3aa/0x1f70 [nvidia_modeset] [412515.698246] ? __alloc_pages_nodemask+0x173/0x320 [412515.698248] ? alloc_pages_current+0x87/0xe0 ... ** Tags added: nvidia ** Summary changed: - Display freeze + [nvidia] Display freeze ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: [nvidia] Display freeze Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https:
[Touch-packages] [Bug 1887287] Re: No show-desktop shortcut out of the box since 18.04
Super-D does work correctly in Ubuntu 20.04 at least. I just tested it. As for Ubuntu 19.10, that is about to reach end of life: https://wiki.ubuntu.com/Releases so any bugs in 19.10 won't get fixed. Please install Ubuntu 20.04 instead. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1887287 Title: No show-desktop shortcut out of the box since 18.04 Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at almost every major release, which was already irritating enough, but at least there always was one. Now, however, there doesn't seem to be any half-discoverable keyboard shortcut to show the desktop. I have tried Super+D, Ctrl+Alt+D (both mentioned in a bullshit article I found out by googling), and every other similar combination I can think of involving a D. Nothing works. I shouldn't have to install a tool and create a shortcut to it just to reveal the desktop. It's something basic. Especially considering that it used to be available out of the box. So sick of Ubuntu going backwards. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:30:58 2020 DistUpgraded: 2020-07-12 15:02:52,488 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jul 12 15:12:31 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed
[Touch-packages] [Bug 1887254] Re: The new design makes maximized windows unusable
*** This bug is a duplicate of bug 1710353 *** https://bugs.launchpad.net/bugs/1710353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1710353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1710353 Window controls and menus aren't in top bar when app is maximized -- 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/1887254 Title: The new design makes maximized windows unusable Status in xorg package in Ubuntu: New Bug description: I have just upgraded from ubuntu 16.04 to 18.04 (and I would have upgraded to 20.04 already if the stupid package manager weren't unable to resolve some conflicts which are "holding back" packages). An unbelievavly stupid mistake was made in the new design of windows. When you maximize a window, the title bar used to be at the very top of the screen, and the close/minimize/restore buttons used to be at the top-left corner of the screen. That means they had a property that in interface design has even a name, "infinite width" or "infinite something", that is: you can move the mouse all the way to the top and all the way to the left without having to "stop at the right time" in order to "land" within the area of the button, because the screen edges limit the mouse cursor. Now, the title bar of the window is no longer at the very top of the screen. At the top of the screen is a system bar. I mean that was already there, but the window buttons used to be in it on the left, as if the system bar at the top of the screen *was* the window title bar. Now the window title bar is just below it, and the buttons have been moved to the right (the fact that they have been moved from the left to the right after decades being on the left is irritating AF, but it's irrelevant here). So now the buttons, while still at the horizintal edge of the screen, are no longer at the corner of the screen, so when you "shoot" the mouse pointer to go to their area, you cannot simply go as far as you can and then click, you have to move a little bit down from the top in order to click the buttons. It's not just an aesthetic thing, it's a huge usablility thing. And it's not just a matter of habits and getting used to, it's objectively a step backwards (actually, it's a step in a completely new dimension, one of stupidity). It violates a very well known UI design principle that has been established for decades - and for a good reason, not just for historical reasons. Please revert this madness. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 22:32:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bi
[Touch-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade
Please open: Gnome Tweaks > Fonts and check that you are using 'Ubuntu' fonts. ** Package changed: xorg (Ubuntu) => pango1.0 (Ubuntu) ** Summary changed: - Square rectangles instead of system fonts after upgrade + Square rectangles instead of system fonts after upgrade (LANG=de_AT.UTF-8) ** Changed in: pango1.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1887271 Title: Square rectangles instead of system fonts after upgrade (LANG=de_AT.UTF-8) Status in pango1.0 package in Ubuntu: Incomplete Bug description: After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04 Focal Fossa (from Bionic 18.04): Any system font line is being displayed distorted / erroneous / in sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't be installed at all... Tthe 'gsettings'-procedure from some link mentioned on askubuntu-com wouldn't help either (with copy&paste into unreadable terminal display font output) Gnome-tweak didn't help, BUT I can copy text from terminal into libreoffice document and thus make it readable afterwards. I cannot find any information about "system font output/printing" on the whole internet leaving me with a mysrltery about how that stuff works from xserver to gnome, Wayland- session login IMPOSSIBLE in order to print the correct display font ... I will attach some screenshots later on if possible. P.S.: firefox/libreoffice fonts are being displayed correctly inside any homepage ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 10:55:08 2020 DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed rtlwifi-new, 0.10: added GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801] InstallationDate: Installed on 2017-08-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+6033.49s] DEBUG: Seat seat0 changes active session to [+6033.53s] DEBUG: Seat seat0 changes active session to c5 [+6033.53s] DEBUG: Session c5 is already active MachineType: FUJITSU SIEMENS ESPRIMO P ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago) dmi.bios.date: 10/11/2007 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.12.2312.A3 dmi.board.name: D2312-A3 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2312-A3 dmi.chassis.type: 2 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPP dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP: dmi.product.name: ESPRIMO P dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 11 20:24:02 2020 xserver.configfile: /etc/X11/xorg.conf xserver.err
[Touch-packages] [Bug 1887208] Re: May be xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1887208 Title: May be xorg Status in Ubuntu: Incomplete Bug description: My system reports something problem. Saying xorg crash ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jul 11 10:45:09 2020 DistUpgraded: 2020-07-05 12:47:35,837 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: ./xorg_fix_proprietary.py を子プロセスとして起動できませんでした: No such file or directory (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2015-09-24 (1751 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Build amd64 LIVE Binary 20140422-09:40 MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=1f04dac6-7535-44a7-8ea2-e3d566af9feb ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-07-05 (5 days ago) dmi.bios.date: 04/08/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97M-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.:bvr3602:bd04/08/2018:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH97M-PLUS:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Jul 5 11:17:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887208/+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 1887247] Re: Annoying drum sound that I turned off ages ago has turned on again after upgrade
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1887247 Title: Annoying drum sound that I turned off ages ago has turned on again after upgrade Status in gnome-shell package in Ubuntu: New Bug description: I have just upgraded from 16.04 to 18.04 Now, every time I hit the TAB key in a terminal to autocomplete a file name, when there is no option or more than one, an annoying and ungodly loud drum sound plays. I'm pretty sure I disabled that sound years ago, probably even before I even upgraded to 16.04. I don't want to be forced to re-configure everything. If I turned off a certain kind of system sounds, I expect this configuration to be kept after I upgrade to a newer release. Otherwise I might as well wipe out my hard disk and do a clean install, if you are going to reset my settings anyway. And by the way, if the sound had been chosen with a minimum of taste and was not disproportionately loud (my global volume is pretty low) I probably wouldn't need to turn it off in the first place, as in principle it can be useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 20:48:14 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jul 11 20:18:24 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887247/+subscriptions -- Mailing list: https://launchp
[Touch-packages] [Bug 1887150] Re: Fractional Scaling turns screen sideways
** Tags added: xrandr-scaling ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887150 Title: Fractional Scaling turns screen sideways Status in mutter package in Ubuntu: New Bug description: I right-click on desktop, click Display Settings, and find the Fractional Scaling option. When I enable the option my screen rotates 90 degrees. It's as if the display thought I had rotated my device 90 degrees (but I hadn't I'm using a laptop). Can attach screenshots if possible. I just freshly installed Ubuntu 20.04 from a USB and ran sudo apt-get update and sudo apt-get upgrade for the first time literally minutes ago. Nothing else was installed except for Grub Customizer and EDIT: Turns out I can't attach three screenshots. I can only attach one. I attached the final screenshot. I took screenshots of the original rotation, then before I selected the Fractional Scaling option, then what happened after. But I can only attach one of them. Please allow us to attach more than one screenshot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 06:34:56 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:19d1] InstallationDate: Installed on 2020-07-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b568 Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop TP412FA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=d20ac799-f93e-4aea-9632-495aa9132b04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP412FA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP412FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP412FA.302:bd05/06/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopTP412FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP412FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: VivoBook Flip dmi.product.name: VivoBook_ASUSLaptop TP412FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1887150/+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 1887198] Re: [Raspberry Pi 4] Screen Freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Screen Freeze + [Raspberry Pi 4] Screen Freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1887198 Title: [Raspberry Pi 4] Screen Freeze Status in Ubuntu: Incomplete Bug description: When changing user or logging off of ubuntu-desktop got a screen freeze that I can't get out of. No response from keyboard or mouse. After some time screen goes black with cursor flicking at the bottom. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-1013.13-raspi 5.4.44 Uname: Linux 5.4.0-1013-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Fri Jul 10 20:05:57 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: ImageMediaBuild: 20200423.1 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 17ef:600e Lenovo Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:7C:B3:EE vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887198/+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 1887010] Re: problème de démarrage ordinateur lenovo G50
It appears we do not yet have a full log from this machine. Next time the problem happens, please run: journalctl -b0 > journal.txt and then attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1887010 Title: problème de démarrage ordinateur lenovo G50 Status in Ubuntu: Incomplete Bug description: Bonjour, En marche, l'ordinateur avec ubuntu 18.04 fonctionne très bien. Il s'éteint facilement. Pour le re démarrer, l'écran reste noir très longtemps, parfois pendant une heure avant de retrouver le bureau et re fonctionner normalement. Le disque dur fonctionne normalement, la barette mémoire aussi que j'ai testé en la remplaçant par une neuve: le problème reste. Je ne comprends pas la cause de ce problème. Pouvez vous m'aider? Merci Hello, When running, the computer with ubuntu 18.04 works very well. It goes out easily. To restart it, the screen remains black for a very long time, sometimes for an hour before finding the office and re-operating normally. The hard drive works normally, the memory module also that I tested by replacing it with a new one: the problem remains. I do not understand the cause of this problem. Can you help me? Thank you (I do not understand English) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-106.107-generic 4.15.18 Uname: Linux 4.15.0-106-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 9 21:48:34 2020 DistUpgraded: 2019-08-20 08:07:14,386 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:390c] Subsystem: Lenovo Radeon R5 M330 [17aa:390c] InstallationDate: Installed on 2019-08-14 (330 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: LENOVO 80E5 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-106-generic root=UUID=5732a78d-7e74-4071-9c56-b93ae51ffae3 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-20 (324 days ago) dmi.bios.date: 07/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B0CN93WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo G50-80 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-80 dmi.modalias: dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoG50-80: dmi.product.family: IDEAPAD dmi.product.name: 80E5 dmi.product.version: Lenovo G50-80 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jun 24 22:12:46 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887010/+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 1887018] Re: Xorg crash when I was using Visual Studio code, throwing me back to the login screen
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1887018 Title: Xorg crash when I was using Visual Studio code, throwing me back to the login screen Status in Ubuntu: Incomplete Bug description: Sometimes, when this happens, the computer goes to sleep too. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Thu Jul 9 17:47:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] InstallationDate: Installed on 2020-07-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5570 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=b7d02d55-0b33-48b4-8eb2-5217925c5f81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.5 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.5:bd02/20/2020:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887018/+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 1887001] Re: Mouse suddenly stopped working
Please try these, in any order: 1. Replacing the batteries in your wireless mouse. 2. A wired mouse. 3. sudo apt remove xserver-xorg-input-synaptics ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Package changed: xorg-server (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887001 Title: Mouse suddenly stopped working Status in Ubuntu: Incomplete Bug description: Mouse suddenly stopped working and didn't fix even after a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 19:40:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics Controller [103c:146a] InstallationDate: Installed on 2019-05-02 (434 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a3b4ba1a-5361-47c5-9d78-b04d395d28b8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 146A dmi.board.vendor: Hewlett-Packard dmi.board.version: 58.27 dmi.chassis.asset.tag: CNU0483ZXV dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr058B11242B1020100:rvnHewlett-Packard:rn146A:rvr58.27:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dm4 Notebook PC dmi.product.sku: XH124UA#ABA dmi.product.version: 058B11242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1887001/+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 1877540] Re: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877540 Title: [HDA-Intel - HDA Intel, playback] volume slider problem for subwoofer Status in alsa-driver package in Ubuntu: Expired Bug description: In standard Ubuntu volume settings subwoofer level is alwas set to zero and i cant change it if i run pavucontrol and set separate levels for each channel it works, sound is working, but if i open ubuntu sound settings and touch subwoofer level control then level is instantly set to zero again once i was unable to change subwoofer level in pavucontrol while ubuntu sound settings is opened. after it is closed i can change voluve level of sub before I install pavucontrol front speaker was very quiet nearly mute also in test speakers there is no icon on subwoofer button ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-52.46-generic 5.3.18 Uname: Linux 5.3.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 8 11:00:18 2020 InstallationDate: Installed on 2018-03-04 (795 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180228) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Dell USB3.0 Dock - Dell USB3.0 Dock Symptom_PulseAudioLog: мая 08 10:26:20 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.36' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") мая 08 10:26:27 tmpuser-EP43-UD3L dbus-daemon[1168]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.135' (uid=119 pid=1422 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [HDA-Intel - HDA Intel, playback] volume slider problem UpgradeStatus: Upgraded to eoan on 2019-11-07 (183 days ago) dmi.bios.date: 04/16/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP43-UD3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd04/16/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP43-UD3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP43-UD3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP43-UD3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877540/+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 1886714] Re: Bluetooth disconnects, and then sound fails on reconnect
Thanks. Please also try to describe the problem (and only one problem) in a couple of sentences or less and put that at the top of the bug. ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1886714 Title: Bluetooth disconnects, and then sound fails on reconnect Status in bluez package in Ubuntu: New Bug description: This bug has persisted over several years, and several versions, and after a lot of investigation I'm not really any closer on what's going on. I have two pretty old GA MA78gm S2H mainboards, configured slightly different, and otherwise working properly. Both of them have run both Ubuntu and Windows. The problem seems to have been minimized when running Win10, and even if it is there it seems like Win10 recover when it happen. I wonder if I started noticing the problem under Ubuntu 14.x, but I'm pretty sure it was there already at Ubuntu 16.x. I'm now running Ubuntu 19.10 and Gnome 3.34.2. (Just for the record, the bug also persisted in Ubu 18.04 for as long as I was using it.) It isn't really an option to switch the mainboards, as there are too much custom-builds running on them for the moment. They will probably be replaced when I have time to rebuild everything. ;) To make Bluetooth work I use an ASUS USB-BT400, which report as “BCM920702 Bluetooth 4.0”, or more accurately “BCM20702A1 (001.002.014) build 1467”. I have also used other dongles, but it seems like all of them has the same chipset. Now… Given I restart the computer And boot into Ubuntu 19.10 And log in as myself And attach a pair of Sony MDR-ZX770BN When I listen to sound from a movie with A2DP Then at some random point it start to lag noticeably (sound becomes scratchy) And suddenly disconnects (at this point it seems like it is Bluetooth that disconnects) It may take 5–10 minutes and up to several hours before it disconnects. Given I turn the headphones off And back on When it reconnects to the computer Then the computer fails to enable the sound device (visible in the preference manager f.ex.) There are several reports of various equipments that disconnect, and I wonder if this could be the same problem. Problem 1 The dongle is rather hot when it disconnects. This is mere speculation, but I wonder if the disconnect happen because either the mainboard gives to little current and thus it fails due to voltage drop, or it fails due to overheating. It seems like the port should have enough current to sustain the dongle, but I wonder if the mainboard could let several ports share the same power source, and thus it fail to deliver enough current. There are other devices powered by the USB ports, and they don't seem to fail, which seems likely to happen if power is the issue. The issue seems to be somewhat related to the quality of the audio, which makes me wonder whether higher quality gives more transferred data, which again gives higher power consumption. It also seems like the issue can be triggered by moving away from the computer. That would give higher tx power, which could make the dongle overheat or mainboard could fail to provide enough current. Is there any way to get a more specific failure report from the dongle? Problem 2 After the headphone reconnects it seems like the sound system isn't working properly. I've been checking, and everything seems correct, still the headphone is missing as an output device. I have not been able to figure out what makes the sound system fail, and I have not been able to make it recover. Only way to recover seems to be to do a cold reboot. A simple warm reboot does not fix the problem, but this can be related to problem 1. A few dumps john@hydra:~$ dmesg | fgrep 'Blue' [3.089584] usb 1-2.2: Product: BCM920702 Bluetooth 4.0 [8.417252] Bluetooth: Core ver 2.22 [8.417280] Bluetooth: HCI device and connection manager initialized [8.417284] Bluetooth: HCI socket layer initialized [8.417286] Bluetooth: L2CAP socket layer initialized [8.417301] Bluetooth: SCO socket layer initialized [8.779706] Bluetooth: hci0: BCM: chip id 63 [8.780703] Bluetooth: hci0: BCM: features 0x07 [8.796682] Bluetooth: hci0: hydra [8.800667] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.671568] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467 [9.687584] Bluetooth: hci0: Broadcom Bluetooth Device [ 10.571440] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.571442] Bluetooth: BNEP filters: protocol multicast [ 10.571448] Bluetooth: BNEP socket layer initialized [ 630.835385] Bluetooth: RFCOMM TTY layer initialized [ 630.835393] Bluetooth: RFCOMM socket layer initialized [ 630.835398] Blueto
[Touch-packages] [Bug 1068222] Re: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
P.S. OS is recently installed Linux Mint 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1068222 Title: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in console-setup package in Ubuntu: Confirmed Bug description: no able to delete gnu gettext ProblemType: Package DistroRelease: Ubuntu 12.04 Package: console-setup 1.70ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu13 AptOrdering: gettext: Remove console-setup: Configure ubuntu-minimal: Configure Architecture: amd64 Date: Thu Oct 18 20:52:02 2012 DuplicateSignature: Setting up console-setup (1.70ubuntu5) ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist. dpkg: error processing console-setup (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all SourcePackage: console-setup Title: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2012-08-25 (54 days ago) modified.conffile..etc.console.setup.remap.inc: [deleted] modified.conffile..etc.console.setup.vtrgb: [deleted] modified.conffile..etc.console.setup.vtrgb.vga: [deleted] modified.conffile..etc.init.setvtrgb.conf: [deleted] mtime.conffile..etc.init.console.setup.conf: 2010-12-21T18:50:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1068222/+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 1068222] Re: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I had the issue. After trying different things I created two files, vtrgb and vtrgb.vga as per https://www.apt- browse.org/browse/ubuntu/bionic/main/all/console-setup- linux/1.178ubuntu2/file/etc/console-setup (even though I am on Focal Fossa) and placed them at /etc/console-setup/ . I ran sudo dpkg --configure -a and the error was gone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1068222 Title: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in console-setup package in Ubuntu: Confirmed Bug description: no able to delete gnu gettext ProblemType: Package DistroRelease: Ubuntu 12.04 Package: console-setup 1.70ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu13 AptOrdering: gettext: Remove console-setup: Configure ubuntu-minimal: Configure Architecture: amd64 Date: Thu Oct 18 20:52:02 2012 DuplicateSignature: Setting up console-setup (1.70ubuntu5) ... update-alternatives: error: alternative path /etc/console-setup/vtrgb doesn't exist. dpkg: error processing console-setup (--configure): subprocess installed post-installation script returned error exit status 2 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) PackageArchitecture: all SourcePackage: console-setup Title: package console-setup 1.70ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to precise on 2012-08-25 (54 days ago) modified.conffile..etc.console.setup.remap.inc: [deleted] modified.conffile..etc.console.setup.vtrgb: [deleted] modified.conffile..etc.console.setup.vtrgb.vga: [deleted] modified.conffile..etc.init.setvtrgb.conf: [deleted] mtime.conffile..etc.init.console.setup.conf: 2010-12-21T18:50:22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1068222/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
@chih it's uploaded, at this point it's waiting for review by the ~ubuntu-sru team. Out of my hands now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms Status in HWE Next: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Committed Bug description: [Impact] Press wireless hotkey on HP's latest generation laptops generate two rfkill events, prevent airplane mode from turning off. One event is from intel-hid and the other one is from hp-wireless. [Fix] Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use rfkill from hp-wireless. [Test] With the one-liner fix, press wireless hotkey only generate one rfkill event, hence airplane mode works as expected. [Regression Potential] Low, use hp-wireless over intel-hid is anticipated. any regression would likely result in missed rfkill events. [scope] this is fixed upstream by commit d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any version yet, so this is needed for f and g. @kaihengfeng is this needed on b and/or x as well? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 938751] Re: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome)
That flag is still available in Chrome at least :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/938751 Title: Images are washed out or colors are skewed in some apps (particularly Image Viewer and Chrome) Status in Eye of GNOME: New Status in GNOME Shell: Unknown Status in chromium-browser package in Ubuntu: Confirmed Status in colord package in Ubuntu: Confirmed Status in eog package in Ubuntu: Confirmed Status in inkscape package in Ubuntu: Confirmed Bug description: Images are washed out or colors are skewed in some apps, notably Chrome/Chromium and Image Viewer (eog). Workaround: Settings > Devices > Colour > and disable or remove your monitor's colour profile To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/938751/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms
@Dan, can you let us know when we can expect the fix to land on Focal please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1883846 Title: hwdb: Mask rfkill event from intel-hid on HP platforms Status in HWE Next: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Focal: In Progress Status in systemd source package in Groovy: Fix Committed Bug description: [Impact] Press wireless hotkey on HP's latest generation laptops generate two rfkill events, prevent airplane mode from turning off. One event is from intel-hid and the other one is from hp-wireless. [Fix] Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use rfkill from hp-wireless. [Test] With the one-liner fix, press wireless hotkey only generate one rfkill event, hence airplane mode works as expected. [Regression Potential] Low, use hp-wireless over intel-hid is anticipated. any regression would likely result in missed rfkill events. [scope] this is fixed upstream by commit d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any version yet, so this is needed for f and g. @kaihengfeng is this needed on b and/or x as well? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1820866] Re: File dialog extremely slow scanning network mounts
I have the same problem when running gedit on Windows 10. The problem started when I started working from home using a VPN to connect to the network and shared drives at work. Because I access the shared drives over a VPN, scanning them by gedit takes a very long time; around 10 seconds. Accessing the shared drives using Windows Explorer and other file operations (like copy) also take very long. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1820866 Title: File dialog extremely slow scanning network mounts Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: From any application where you have a "save as" or "open" option, the dialog displays, but it takes forever. I have a i5 with 16GB RAM and 2 SSD's, so the machine is not slow. However, if I use gedit and click open / Other documents it takes 6 to 7 seconds before the file dialog is properly displayed. This does not even get better with reuse. I opened gedit just now and the first time it took 7 seconds. Then I pressed Cancel and repeated the process - it still took more than 6 seconds before the dialog was properly displayed. Often I would only see "Other locations" and then default places (Home, Documents etc) and bookmarks (I have about 8 bookmarks of which 2 are network shares) are displayed. These items are added one by one - maybe one every half second. Often it takes a few seconds before the first location other than "Other Locations" is displayed. Even the file panel is not immediate at first and you can see how lines are added one by one. Take into account that my home folder is on an SSD, so populating a file list should be lightning fast. I have looked at the CPU activity, but it does not go over about 10% during display of open and close dialogs. Just be aware that this is not specific to gedit - all applications using gnome file dialog has the same problem. Please see the attached screen recording. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 19 16:14:16 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['nohotcor...@azuri.free.fr', 'weather-extens...@xeked.com', 'openweather-extens...@jenslody.de']" b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2018-12-02 (107 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1820866/+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 1887304] [NEW] Display configuration gets applied only after I log in
Public bug reported: This isn't new, this idiocy has annoyed me ever since I've been using Ubuntu; however, after upgrading to 20.04 I'm disappointed to see that it still hasn't been fixed. I use a laptop and I have an external monitor that I keep connected most of the time. So, I have it set up to use the external screen as the only display. However, when I boot and the login screen shows up, a different configuration, which I guess is the default, is applied, with the laptop's built-in display as the main display and the external screen as the secondary one in extended desktop configuration. Therefore the login screen shows up on the builtin display. Only after I log in, my configuration gets applied and the builtin displey turns off and the external one becomes the only one. It's not a huge deal since the laptop screen is kind of in front of me anyway so I can see it, but it's not ideal and it's stupid. Also, it implies that when I do log in, I have that few seconds of all-black screens while the displays adjust, which is irritating considered they would have had plenty of time to do that before I logged in. I guess the display configuration is somehow stored as associated to the user, and I understand that theoretically different users may have different configurations. However, that's no excuse. As an administrator, I should be able to choose a configuration that gets applied from the beginning before anybody logs in. Also, given that I am the ONLY user (which is a pretty common scenario on Desktop), it should be the default that my configuration be the global configuration (with the possibility to choose differently). Probably a good solution would be to have, in the Displays settings, an option such as "apply this configuration globally" (or whatever better phrasing), meaning it would be applied before login. Obviously that doesn't mean that, if the saved configuration is not applicable to the current situation at startup (e.g. I have set it up to use only the external monitor but there is no external monitor connected right now), it shouldn't automatically switch to a different workable setting. I think it already does that if that happens after login, so that would be no different before login. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 21:04:20 2020 DistUpgraded: 2020-07-12 20:55:12,554 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2466 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa
[Touch-packages] [Bug 1887296] [NEW] Moving popup windows drags the application's main window behind it
Public bug reported: Sometimes programs open a "popup" or a "secondary", "child" window, I don't know what the word is. For example, in Chrome, if I right-click on an image in a web page and choose "Save As", this will open a new file browser window that allows me to browse for a directory to save the image to. Until Ubuntu 16.04, I could move that child window around by dragging it by its title bar, and that would not move around the parent window behind it. Now, it does. That is, the "parent" window greyes out, and moving the "child" window (i.e. the popup) on the foreground causes the parent window in the background to move as if they were glued together. In the above example, if I drag around the "Save As" window, the Chrome window behind it moves too. Even worse, if the parent window is maximized, it will "oppose resistance" to the dragging of the popup window, and if I drag far enough, the parent window will unmaximize and unblock the movement of both windows. It's pure madness. I can't imagine a scenario where this is the unavoidable consequence of some improvement. It looks like it is by design. Why? What were you thinking? Why do you ACTIVELY work to degrade usability and make the users' life miserable?? Here's a very real-life example: As mentioned above, I right-click on something in the browser (like an image or a video) and do Save As. When the file browser window opens, it covers the content of the web page from which I was saving the content. Maybe I want to move the child window in order to reveal the web page that I was visiting in the first place, because the context (which I haven't memorized in full in my brain just yet) helps me choose a file name for the very file I'm saving. Another example: I am browsing some folder in Nautilus. I right-click on a file or folder inside it, and open Properties. That opens in a popup. Now I want to have another look at the name of the file I selected (of which I'm now seeing the properties), and those around it, because I'm wondering if I chose the wrong file, or for whatever other reason. I can't do taht without closing the Properties window. The everyday examples are countless. This is idiotic. Seriously, what are you doing? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 18:11:28 2020 DistUpgraded: 2020-07-12 15:56:23,368 INFO cache.commit() DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108: added ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-x
[Touch-packages] [Bug 1887294] [NEW] Display freeze
Public bug reported: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: Display freeze Status in xorg package in Ubuntu: New Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19u
[Touch-packages] [Bug 1887289] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1
Public bug reported: System version detection falsh ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 12 16:22:11 2020 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2019-10-17 (268 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1887289 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 Status in initramfs-tools package in Ubuntu: New Bug description: System version detection falsh ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Jul 12 16:22:11 2020 ErrorMessage: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 InstallationDate: Installed on 2019-10-17 (268 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: 已安装 initramfs-tools 软件包 post-installation 脚本 子进程返回错误状态 1 UpgradeStatus: Upgraded to focal on 2020-07-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1887289/+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 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
Just an FYI. `apt`, `apt-get`, `dpkg` etc are all package tools that share a package database, so your installation of a package with dpkg is linked to apt- get & like package tools. To view reference details about commands, I'd suggest trying the `man` command which will view the manual (reference) pages on your system (these can be viewed with a browser too; eg. http://manpages.ubuntu.com/manpages/bionic/man8/apt-get.8.html), or perhaps you could try the Ubuntu wiki - https://help.ubuntu.com/community/AptGet/Howto or search online for guides... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887277 Title: apt-get install REMOVES packages without replacing them and with barely any warning Status in apt package in Ubuntu: Invalid Bug description: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: ** * A T T E N T I O N * ** * The following packages will be REMOVED* ** * and NO SUITABLE REPLACEMENT will be installed * ** ** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that supersedes it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatialite7 libsuperlu5 libsz2 liburiparser1 linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 proj-bin proj-data Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly instal
[Touch-packages] [Bug 1887288] [NEW] upgrade to 19.10 seemed to finish silently with no confirmation nor error message
Public bug reported: On Ubuntu 18.04, Software Updater informed me that an upgrade to 19.10 was available, so I chose "Upgrade". The process went reasonably smoothly (except for a "system problem detected" popup at the very beginning, that happens all the time - we are talking "ubuntu" smoothly). In the "Distribution Upgrade" window, the steps "Preparing to Upgrade" and "Setting new software channels" got checked pretty quickly, then "Getting new packages" took several minutes, and then "Installing the upgrades" went on for a few hours, with the progress bar slowly but steadily growing. When the progress bar was almost full, near the end, for some reason it went back to the beginning, while still at the stage "Installing the upgrades". As if the "installing the upgrades" stage had restarted from scratch. That, alone, is a bug. But then, several minutes later, I got distracted, and when I came back, the window was gone. There was absolutely nothing on the screen regarding the upgrade process. Not an error message, not a confirmation message saying the upgrade was complete. I couldn't tell whether it was finished without any confirmation message, or if it had crashed and failed with no error message, or if it was processing something and a new window was going to pop up at any moment, without any "loading" or "wait" indicator. None of the three scenarios is acceptable. I waited a while, also I opened a terminal and had a look at running processes to see if there was something that looked like it could be upgrade-related, and couldn't find any. After several minutes of no apparent activity, I restarted. At first, the system got stuck at a black screen with a blinking cursor (just after selecting Ubuntu from the boot menu). I thought the distributioon upgrade had bricked my computer like almost every time in the past. But fortunately no. I powered it down and restarted again, and it succesfully booted to what it seems to be a fully functional 19.10 (of course, we are talking "ubuntu fully functional"). Pathetic, as usual. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: apt 1.9.4ubuntu0.1 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:44:39 2020 InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887288 Title: upgrade to 19.10 seemed to finish silently with no confirmation nor error message Status in apt package in Ubuntu: New Bug description: On Ubuntu 18.04, Software Updater informed me that an upgrade to 19.10 was available, so I chose "Upgrade". The process went reasonably smoothly (except for a "system problem detected" popup at the very beginning, that happens all the time - we are talking "ubuntu" smoothly). In the "Distribution Upgrade" window, the steps "Preparing to Upgrade" and "Setting new software channels" got checked pretty quickly, then "Getting new packages" took several minutes, and then "Installing the upgrades" went on for a few hours, with the progress bar slowly but steadily growing. When the progress bar was almost full, near the end, for some reason it went back to the beginning, while still at the stage "Installing the upgrades". As if the "installing the upgrades" stage had restarted from scratch. That, alone, is a bug. But then, several minutes later, I got distracted, and when I came back, the window was gone. There was absolutely nothing on the screen regarding the upgrade process. Not an error message, not a confirmation message saying the upgrade was complete. I couldn't tell whether it was finished without any confirmation message, or if it had crashed and failed with no error message, or if it was processing something and a new window was going to pop up at any moment, without any "loading" or "wait" indicator. None of the three scenarios is acceptable. I waited a while, also I opened a terminal and had a look at running processes to see if there was something that looked like it could be upgrade-related, and couldn't find any. After several minutes of no apparent activity, I restarted. At first, the system got stuck at a black screen with a blinking cursor (just after selecting Ubuntu from the boot menu). I thought the distributioon upgrade had bricked my computer like almost every time in the past. But fortunately no. I powered it down and restarted again, and
[Touch-packages] [Bug 1835604] Re: usbmuxd: libssl.so.1.0.0: cannot open shared object file
It seems you have installed usbmuxd from a ppa or manually. It's installed in /usr/local/sbin/ whereas in official package the location is /usr/sbin/ ** Changed in: usbmuxd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1835604 Title: usbmuxd: libssl.so.1.0.0: cannot open shared object file Status in usbmuxd package in Ubuntu: Invalid Bug description: After upgrading from xenial to disco, I got the follwing error: /usr/local/sbin/usbmuxd: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file or directory ldd -r /usr/local/sbin/usbmuxd linux-vdso.so.1 (0x7fffa2f8a000) libusb-1.0.so.0 => /lib/x86_64-linux-gnu/libusb-1.0.so.0 (0x7f00e2d7a000) libimobiledevice.so.6 => /usr/local/lib/libimobiledevice.so.6 (0x7f00e2b57000) libplist.so.3 => /usr/local/lib/libplist.so.3 (0x7f00e2948000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f00e2927000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f00e273c000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f00e2716000) libssl.so.1.0.0 => not found libcrypto.so.1.0.0 => not found libusbmuxd.so.4 => /usr/local/lib/libusbmuxd.so.4 (0x7f00e250c000) /lib64/ld-linux-x86-64.so.2 (0x7f00e31d4000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f00e2501000) undefined symbol: ERR_remove_thread_state, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_CTX_use_RSAPrivateKey, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: CRYPTO_cleanup_all_ex_data, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: EVP_PKEY_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: PEM_write_bio_X509, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notAfter, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: ASN1_INTEGER_set, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_set_notBefore, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: RSA_new, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: BIO_s_mem, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: RSA_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_set_bio, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_COMP_get_compression_methods, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_read, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509V3_EXT_conf_nid, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: BN_new, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: CRYPTO_set_id_callback, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: BIO_new_mem_buf, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_write, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_shutdown, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509V3_EXT_cleanup, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: ASN1_TIME_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: EVP_cleanup, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: BIO_s_socket, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: EVP_PKEY_assign, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_set_verify, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: PEM_read_bio_X509, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_set_connect_state, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: X509_EXTENSION_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_do_handshake, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: TLSv1_method, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined symbol: SSL_CTX_free, version OPENSSL_1.0.0 (/usr/local/lib/libimobiledevice.so.6) undefined sym
[Touch-packages] [Bug 1887287] [NEW] No show-desktop shortcut out of the box since 18.04
Public bug reported: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was changed at almost every major release, which was already irritating enough, but at least there always was one. Now, however, there doesn't seem to be any half-discoverable keyboard shortcut to show the desktop. I have tried Super+D, Ctrl+Alt+D (both mentioned in a bullshit article I found out by googling), and every other similar combination I can think of involving a D. Nothing works. I shouldn't have to install a tool and create a shortcut to it just to reveal the desktop. It's something basic. Especially considering that it used to be available out of the box. So sick of Ubuntu going backwards. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-62.56-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:30:58 2020 DistUpgraded: 2020-07-12 15:02:52,488 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed nvidia-340, 340.108, 5.3.0-62-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2020-07-12 (0 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Jul 12 15:12:31 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.5+git20191008-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887287 Title: No show-desktop shortcut out of the box since 18.04 Status in xorg package in Ubuntu: New Bug description: On Ubuntu 16.04 I was used to the keyboard shortcut ctrl+Super+D to reveal the Desktop by minimizing all windows (it was not exactly the same as minimizing all windows but whatever). That shortcut was chan
[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
You not liking apt's solution and only realizing that after you confirmed and applied it is not a bug in apt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887277 Title: apt-get install REMOVES packages without replacing them and with barely any warning Status in apt package in Ubuntu: Invalid Bug description: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: ** * A T T E N T I O N * ** * The following packages will be REMOVED* ** * and NO SUITABLE REPLACEMENT will be installed * ** ** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that supersedes it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatialite7 libsuperlu5 libsz2 liburiparser1 linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 proj-bin proj-data Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. Need to get 1.178 kB of archives. After this operation, 248 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-graphical amd64 1:0.8.2-10build4 [193 kB] Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-common amd64 1:0.8.2-10build4 [771 kB] Get:3 http://es.archive.ubuntu.com/ubuntu bio
[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
What's invalid about this?? ** Description changed: I did: - $ sudo apt-get install ettercap-common + $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) - and I got: - Reading package lists... Done - Building dependency tree - Reading state information... Done - The following packages were automatically installed and are no longer required: - [...] - Use 'sudo apt autoremove' to remove them. - The following additional packages will be installed: - ettercap-graphical libcurl4 - The following packages will be REMOVED: - libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! - The following NEW packages will be installed: - libcurl4 - The following packages will be upgraded: - ettercap-common ettercap-graphical - 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. + Reading package lists... Done + Building dependency tree + Reading state information... Done + The following packages were automatically installed and are no longer required: + [...] + Use 'sudo apt autoremove' to remove them. + The following additional packages will be installed: + ettercap-graphical libcurl4 + The following packages will be REMOVED: + libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! + The following NEW packages will be installed: + libcurl4 + The following packages will be upgraded: + ettercap-common ettercap-graphical + 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. - - I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. + I didn't notice the part that said that some apparently unrelated + packages, one of which I had installed manually (Virtual Box) would be + removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: - *** - * A T T E N T I O N * - * * - * If you proceed, the following packages will be REMOVED * - * * - * and NO SUITABLE REPLACEMENT will be installed * - * * - *** + ** + * A T T E N T I O N * + ** + * The following packages will be REMOVED* + ** + * and NO SUITABLE REPLACEMENT will be installed * + ** + ** - Are you REALLY sure you wish to continue? [y/N] + Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) - - NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. + NEVER before, in my entire life, have I ever seen an instance where + "apt-get INSTALL" would REMOVE packages without at the same time + replacing them with some more recent version or something, and even that + is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that - superseeds it. + supersedes it. - Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. - - + Usually the list of stuff, that you're asked confirmation for when + running "apt-get install", only includes stuff to be installed, upgraded + and left untouched, never removed, so I'm used to responding "Yes" + almost automatically. Here's the rest of the output - - - - $ sudo apt-get install ettercap-common + $ sudo apt-get install ettercap-common
[Touch-packages] [Bug 1887271] Re: Square rectangles instead of system fonts after upgrade
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1887271 Title: Square rectangles instead of system fonts after upgrade Status in xorg package in Ubuntu: New Bug description: After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04 Focal Fossa (from Bionic 18.04): Any system font line is being displayed distorted / erroneous / in sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't be installed at all... Tthe 'gsettings'-procedure from some link mentioned on askubuntu-com wouldn't help either (with copy&paste into unreadable terminal display font output) Gnome-tweak didn't help, BUT I can copy text from terminal into libreoffice document and thus make it readable afterwards. I cannot find any information about "system font output/printing" on the whole internet leaving me with a mysrltery about how that stuff works from xserver to gnome, Wayland- session login IMPOSSIBLE in order to print the correct display font ... I will attach some screenshots later on if possible. P.S.: firefox/libreoffice fonts are being displayed correctly inside any homepage ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 10:55:08 2020 DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed rtlwifi-new, 0.10: added GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801] InstallationDate: Installed on 2017-08-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+6033.49s] DEBUG: Seat seat0 changes active session to [+6033.53s] DEBUG: Seat seat0 changes active session to c5 [+6033.53s] DEBUG: Session c5 is already active MachineType: FUJITSU SIEMENS ESPRIMO P ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago) dmi.bios.date: 10/11/2007 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.12.2312.A3 dmi.board.name: D2312-A3 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2312-A3 dmi.chassis.type: 2 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPP dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP: dmi.product.name: ESPRIMO P dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 11 20:24:02 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : http
[Touch-packages] [Bug 1887271] [NEW] Square rectangles instead of system fonts after upgrade
You have been subscribed to a public bug: After upgrading my room mate's Fujitsu Esprimo Desktop PC to 20.04 Focal Fossa (from Bionic 18.04): Any system font line is being displayed distorted / erroneous / in sort of placeholder blocks or SQUARE RECTANGLES, as if the fonts set wouldn't be installed at all... Tthe 'gsettings'-procedure from some link mentioned on askubuntu-com wouldn't help either (with copy&paste into unreadable terminal display font output) Gnome-tweak didn't help, BUT I can copy text from terminal into libreoffice document and thus make it readable afterwards. I cannot find any information about "system font output/printing" on the whole internet leaving me with a mysrltery about how that stuff works from xserver to gnome, Wayland-session login IMPOSSIBLE in order to print the correct display font ... I will attach some screenshots later on if possible. P.S.: firefox/libreoffice fonts are being displayed correctly inside any homepage ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 10:55:08 2020 DistUpgraded: 2020-06-29 10:31:32,274 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.3.0-51-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-39-generic, x86_64: installed nvidia-340, 340.108, 5.4.0-40-generic, x86_64: installed rtlwifi-new, 0.10: added GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G84 [GeForce 8600 GT] [10b0:0801] InstallationDate: Installed on 2017-08-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) LightdmLog: [+6033.49s] DEBUG: Seat seat0 changes active session to [+6033.53s] DEBUG: Seat seat0 changes active session to c5 [+6033.53s] DEBUG: Session c5 is already active MachineType: FUJITSU SIEMENS ESPRIMO P ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz root=/dev/sdb4 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-29 (13 days ago) dmi.bios.date: 10/11/2007 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.12.2312.A3 dmi.board.name: D2312-A3 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2312-A3 dmi.chassis.type: 2 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: ESPP dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.12.2312.A3:bd10/11/2007:svnFUJITSUSIEMENS:pnESPRIMOP:pvr:rvnFUJITSUSIEMENS:rnD2312-A3:rvrS26361-D2312-A3:cvnFUJITSUSIEMENS:ct2:cvrESPP: dmi.product.name: ESPRIMO P dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Jul 11 20:24:02 2020 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal resolution ubuntu -- Square rectangles instead of system fonts after upgrade https://bugs.launchpad.net/bugs/1887271 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
@Bob Lawrence (pilotbob42) So i'm back with a better workaround. First I enabled the intel driver like I specified in my first point.(this removes the tearing) Then I used your workaround, but this was causing the other inputs to error at startup so I on some forum that adding a command at startup applications is a better solution. So i added:"xrandr --output HDMI-3 --mode 1920x1080 --scale 0.x0." as a new command in Startup Applications. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+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 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887277 Title: apt-get install REMOVES packages without replacing them and with barely any warning Status in apt package in Ubuntu: Invalid Bug description: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: *** * A T T E N T I O N * * * * If you proceed, the following packages will be REMOVED * * * * and NO SUITABLE REPLACEMENT will be installed * * * *** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that superseeds it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatialite7 libsuperlu5 libsz2 liburiparser1 linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 proj-bin proj-data Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. Need to get 1.178 kB of archives. After this operation, 248 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-graphical amd64 1:0.8.2-10build4 [193 kB] Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-common amd64 1:0.8.2-10build4 [771 kB]
[Touch-packages] [Bug 1887277] Re: apt-get install REMOVES packages without replacing them and with barely any warning
By the way, VirtualBox is not even something I had installed with apt. I downloaded a .deb and installed it with dpkg or something. Also, I notice that the above command removed libcurl3 and installed libcurl4. That part makes sense. But then it uninstalled php7.2-curl. I guess that was because it depended on libcurl, but then if you uninstall it because you removed libcurl3 and replaced it with libcurl4, you should either find a solution to that (reinstall php7.2-curl? don't remove it in the first place? Install some more recent version that is compatible with libcurl4?? I have no idea, you are the package manager, it's your job) or at least TELL ME ABOUT IT so that I can make an informed decision. And by "tell me" I don't mean "Oh, by the way I'm also gonna remove this stuff", but "Package a will be removed because it depends on package b which will be replaced by package c, however no replacement could be found for package a", or something like that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1887277 Title: apt-get install REMOVES packages without replacing them and with barely any warning Status in apt package in Ubuntu: New Bug description: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: *** * A T T E N T I O N * * * * If you proceed, the following packages will be REMOVED * * * * and NO SUITABLE REPLACEMENT will be installed * * * *** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that superseeds it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatiali
[Touch-packages] [Bug 1878434] Re: xshape - not able to select area on screen
** Changed in: ubuntu-mate Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1878434 Title: xshape - not able to select area on screen Status in Ubuntu MATE: Incomplete Status in libxcb package in Ubuntu: New Bug description: I have problem selecting area on screen with some programs. I am able to select an area on screen with slop (author: Dalton Nell) and not able select with hacksaw (source: https://github.com/neXromancers/hacksaw). reference link : https://github.com/neXromancers/hacksaw/issues/26#issuecomment-613570352 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1878434/+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 1887277] [NEW] apt-get install REMOVES packages without replacing them and with barely any warning
Public bug reported: I did: $ sudo apt-get install ettercap-common (by the way I don't even know what that is, but it is one of a few packages being "held back" by apt and that prevents me from upgrading from 18.04 to 20.04. Since apt itself doesn't give me a clue what to do and there doesn't seem to be a guide anywhere, I'm blindly trying stuff) and I got: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: [...] Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 < NOTE THIS !! The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. I didn't notice the part that said that some apparently unrelated packages, one of which I had installed manually (Virtual Box) would be removed. Technically it asked me for confirmation, but it was in the middle of a bunch of other much more trivial stuff, and you can't just put "REMOVE" in caps and expect me to notice it. If an INSTALL command is going to UNINSTALL something that huge (not just a library that had been installed automatically and is no longer required, but an entire application that I installed manually!), you must give a very specific and explicit prompt (defaulting to No rather than Yes) with a gigantic warning, something like: *** * A T T E N T I O N * * * * If you proceed, the following packages will be REMOVED * * * * and NO SUITABLE REPLACEMENT will be installed * * * *** Are you REALLY sure you wish to continue? [y/N] (possibly red and blinking) NEVER before, in my entire life, have I ever seen an instance where "apt-get INSTALL" would REMOVE packages without at the same time replacing them with some more recent version or something, and even that is rare. I can't see a reason why the installation of a package would require the removal of another, unless it is to replace it with something that superseeds it. Usually the list of stuff, that you're asked confirmation for when running "apt-get install", only includes stuff to be installed, upgraded and left untouched, never removed, so I'm used to responding "Yes" almost automatically. Here's the rest of the output - $ sudo apt-get install ettercap-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: gdal-data libaec0 libaio1 libarmadillo8 libarpack2 libcharls1 libdap25 libdapclient6v5 libepsilon1 libfreexl1 libfyba0 libgeos-3.6.2 libgeos-c1v5 libgeotiff2 libgsasl7 libhdf4-0-alt libhdf5-100 libieee1284-3:i386 libkmlbase1 libkmldom1 libkmlengine1 libkyotocabinet16v5 libminizip1 libnetcdf13 libntlm0 libogdi3.2 libopencv-core3.2 libopencv-imgproc3.2 libopencv-ml3.2 libopencv-video3.2 libproj12 libqhull7 libsdl-ttf2.0-0 libsocket++1 libspatialite7 libsuperlu5 libsz2 liburiparser1 linux-image-4.4.0-142-generic mailutils-common odbcinst odbcinst1debian2 proj-bin proj-data Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: ettercap-graphical libcurl4 The following packages will be REMOVED: libcurl3 php7.2-curl virtualbox-6.0 The following NEW packages will be installed: libcurl4 The following packages will be upgraded: ettercap-common ettercap-graphical 2 upgraded, 1 newly installed, 3 to remove and 6 not upgraded. Need to get 1.178 kB of archives. After this operation, 248 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-graphical amd64 1:0.8.2-10build4 [193 kB] Get:2 http://es.archive.ubuntu.com/ubuntu bionic/universe amd64 ettercap-common amd64 1:0.8.2-10build4 [771 kB] Get:3 http://es.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libcurl4 amd64 7.58.0-2ubuntu3.9 [214 kB] Fetched 1.178 kB in 1s (1.531 kB/s) (Reading database ... 329793 files and directories currently installed.) Removing virtualbox-6.0 (6.0.22-137980~Ubuntu~xenial) ... (Reading database ... 328959 files and directories currently installed.) Preparing to unpack .../ettercap-graphical_1%3a0.8.2-10build4_amd64.deb ... Unpacking ettercap-graphical (1:0.8.2-10build4) over (1:0.8.2-2ubuntu1.16.04.1) ... Preparing to unpack .
[Touch-packages] [Bug 1885474] Re: 1366x768 screen resolution broken, all other resolutions OK
** Tags added: focal ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Also affects: mate-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1885474 Title: 1366x768 screen resolution broken, all other resolutions OK Status in Ubuntu MATE: New Status in libdrm package in Ubuntu: New Status in mate-control-center package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Hi, After upgrade from Ubuntu Mate 19.10 to Ubuntu Mate 20.04 i cannot use a resolution of 1366x768. Screenshot attached. I am using an Asus vivoBook laptop with Amd Ryzen 3 and a Radeon Vega Graphics AMD. I found someone in reddit reporting the same problem: https://www.reddit.com/r/UbuntuMATE/comments/ggq8g5/problem_with_resolution_1366x768_with_ubuntu_mate/ All other screen resolutions OK. Many thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1885474/+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 1887247] Re: Annoying drum sound that I turned off ages ago has turned on again after upgrade
> Note: Please watch your language. They're serious about that here I know, I wish they were half as serious about handling bugs. -- 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/1887247 Title: Annoying drum sound that I turned off ages ago has turned on again after upgrade Status in xorg package in Ubuntu: New Bug description: I have just upgraded from 16.04 to 18.04 Now, every time I hit the TAB key in a terminal to autocomplete a file name, when there is no option or more than one, an annoying and ungodly loud drum sound plays. I'm pretty sure I disabled that sound years ago, probably even before I even upgraded to 16.04. I don't want to be forced to re-configure everything. If I turned off a certain kind of system sounds, I expect this configuration to be kept after I upgrade to a newer release. Otherwise I might as well wipe out my hard disk and do a clean install, if you are going to reset my settings anyway. And by the way, if the sound had been chosen with a minimum of taste and was not disproportionately loud (my global volume is pretty low) I probably wouldn't need to turn it off in the first place, as in principle it can be useful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 20:48:14 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 4.15.0-109-generic, x86_64: installed nvidia-340, 340.108, 4.4.0-185-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0647] NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [10de:1140] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GeForce 710M [1025:0691] InstallationDate: Installed on 2013-10-11 (2465 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Jul 11 20:18:24 2020 xserver.configfile: default xserver.errors: modeset(G0): eglGetDisplay() failed modeset(G0): glamor initialization failed NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1887247/+subscriptions -- Mailing list: https://launchpad.net/~to
[Touch-packages] [Bug 1756574] Re: clock-applet crashed with SIGSEGV in save_cities_store()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1756574 Title: clock-applet crashed with SIGSEGV in save_cities_store() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: after editing my location and then setting the home location the applet crashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: mate-panel 1.20.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: MATE Date: Sat Mar 17 13:56:07 2018 ExecutablePath: /usr/lib/mate-panel/clock-applet InstallationDate: Installed on 2018-03-17 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) ProcCmdline: /usr/lib/mate-panel/clock-applet ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x5605a9f40df5:mov0x0(%r13),%rdi PC (0x5605a9f40df5) ok source "0x0(%r13)" (0x0003) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: clock-applet crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1756574/+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 1874097] Re: brisk-menu crashed with SIGSEGV in brisk_menu_window_filter_section()
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1874097 Title: brisk-menu crashed with SIGSEGV in brisk_menu_window_filter_section() Status in brisk-menu package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: New Bug description: Just the usual Brisk Menu crash, don't really know how that happened, just apport came up and reported the crash. Check included logs for more details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: mate-applet-brisk-menu 0.6.0-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CurrentDesktop: MATE Date: Tue Apr 21 14:24:31 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=C.UTF-8 SegvAnalysis: Segfault happened at: 0x556c50a6e0f0:push %rax PC (0x556c50a6e0f0) in non-executable VMA region: 0x556c504a6000-0x556c50e72000 rw-p [heap] source "%rax" ok destination "(%rsp)" (0x7ffc2919f078) ok SegvReason: executing writable VMA [heap] Signal: 11 SourcePackage: brisk-menu StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_list_box_insert () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_cclosure_marshal_VOID__OBJECTv () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: brisk-menu crashed with SIGSEGV in gtk_list_box_insert() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1874097/+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 1617482] Re: caja crashes when navigating out of waste basket
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1617482 Title: caja crashes when navigating out of waste basket Status in caja package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: New Bug description: navigating out of waste basket, caja crashed with SIGSEGV in gtk_tree_view_insert_column() ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: caja 1.14.2-1 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sat Aug 27 00:32:09 2016 ExecutablePath: /usr/bin/caja InstallationDate: Installed on 2016-08-26 (0 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160824.1) ProcCmdline: caja ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7efdbf5779f0:mov0x18(%rdi),%rax PC (0x7efdbf5779f0) ok source "0x18(%rdi)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: caja StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_tree_view_insert_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () ?? () Title: caja crashed with SIGSEGV in gtk_tree_view_insert_column() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1617482/+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 1757576] Re: mate-tweak crashed with SIGSEGV in settings_backend_path_changed()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1757576 Title: mate-tweak crashed with SIGSEGV in settings_backend_path_changed() Status in glib2.0 package in Ubuntu: New Status in mate-tweak package in Ubuntu: Confirmed Bug description: I'm just trying out mate 18.04 beta. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: mate-tweak 18.04.12-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.389 Date: Thu Mar 22 00:24:49 2018 ExecutablePath: /usr/bin/mate-tweak InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) PackageArchitecture: all ProcCmdline: mate-tweak ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f65e1a02aff:mov0x18(%rax),%rdi PC (0x7f65e1a02aff) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-tweak StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-tweak crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1757576/+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 1664195] Re: mate-panel crashed with SIGSEGV in on_factory_appeared()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1664195 Title: mate-panel crashed with SIGSEGV in on_factory_appeared() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: New Bug description: Tried to "add" date and time to panel. After a delay, it appeared on panel and I was able to input location, 12 hour time, etc. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-panel 1.17.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Mon Feb 13 07:02:57 2017 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2017-02-12 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-panel ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55811d648845:mov0x38(%rax),%rbp PC (0x55811d648845) ok source "0x38(%rax)" (0x0038) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1664195/+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 1841356] Re: username crashed with SIGSEGV in meta_display_list_windows()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1841356 Title: username crashed with SIGSEGV in meta_display_list_windows() Status in glib2.0 package in Ubuntu: New Status in marco package in Ubuntu: Confirmed Bug description: No more information about the crash ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: marco 1.22.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sun Aug 25 10:05:35 2019 ExecutablePath: /usr/bin/marco InstallationDate: Installed on 2019-08-24 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190824) ProcCmdline: username ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb31bfc8dc1 : mov 0x388(%rdi),%rdi PC (0x7fb31bfc8dc1) ok source "0x388(%rdi)" (0x0388) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: marco StacktraceTop: meta_display_list_windows () from /lib/x86_64-linux-gnu/libmarco-private.so.2 meta_display_queue_retheme_all_windows () from /lib/x86_64-linux-gnu/libmarco-private.so.2 ?? () from /lib/x86_64-linux-gnu/libmarco-private.so.2 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: username crashed with SIGSEGV in meta_display_list_windows() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1841356/+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 1727625] Re: mate-appearance-properties crashed with SIGSEGV in g_hash_table_lookup_node()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1727625 Title: mate-appearance-properties crashed with SIGSEGV in g_hash_table_lookup_node() Status in glib2.0 package in Ubuntu: New Status in mate-control-center package in Ubuntu: New Bug description: Just starting to configure 17.10 this is the standard package not the MATE one. May be I mixed up ?? ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-control-center 1.18.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 09:39:07 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/mate-appearance-properties InstallationDate: Installed on 2017-10-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: mate-appearance-properties SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: mate-control-center StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () support_init () Title: mate-appearance-properties crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1727625/+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 1676149] Re: mate-screenshot crashed with SIGSEGV in g_build_filename()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1676149 Title: mate-screenshot crashed with SIGSEGV in g_build_filename() Status in glib2.0 package in Ubuntu: New Status in mate-utils package in Ubuntu: Confirmed Bug description: Keyboard Prt-Scr button doesn't works, and when executing the app by hand, when clicking the "take capture" button the app closes with a core dump. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-utils 1.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sun Mar 26 13:14:37 2017 ExecutablePath: /usr/bin/mate-screenshot InstallationDate: Installed on 2017-03-14 (11 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-screenshot ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f5d92a06f92:cmpb $0x0,(%rax) PC (0x7f5d92a06f92) ok source "$0x0" ok destination "(%rax)" (0x4) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-utils StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_build_filename () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: mate-screenshot crashed with SIGSEGV in g_build_filename() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1676149/+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 1858665] Re: clock-applet crashed with SIGSEGV in claim_op()
** Also affects: glib-networking (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib-networking in Ubuntu. https://bugs.launchpad.net/bugs/1858665 Title: clock-applet crashed with SIGSEGV in claim_op() Status in glib-networking package in Ubuntu: New Status in mate-panel package in Ubuntu: New Bug description: I am running Ubuntu MATE 20.04 64 bit in an older Dell 830 laptop. Yesterday evening I updated the system. Upon opening the laptop lid this morning, I received a notice that clock had quit unexpectedly. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: mate-panel 1.22.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: MATE Date: Tue Jan 7 08:38:33 2020 ExecutablePath: /usr/lib/mate-panel/clock-applet InstallationDate: Installed on 2019-11-12 (55 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191112) ProcCmdline: /usr/lib/mate-panel/clock-applet ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0a44815b33:mov(%rbx),%rax PC (0x7f0a44815b33) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libgiognutls.so g_io_stream_close () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libsoup-2.4.so.1 soup_socket_disconnect () from /lib/x86_64-linux-gnu/libsoup-2.4.so.1 Title: clock-applet crashed with SIGSEGV in g_io_stream_close() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1858665/+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 1547237] Re: mate-panel crashed with SIGSEGV in g_slist_find()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1547237 Title: mate-panel crashed with SIGSEGV in g_slist_find() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: New Bug description: Unknown error. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Thu Feb 18 16:07:43 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-18 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcCmdline: mate-panel ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f61c66a3de0 : cmp %rsi,(%rax) PC (0x7f61c66a3de0) ok source "%rsi" ok destination "(%rax)" (0x0004) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 gtk_rc_get_style () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_find() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: mate-session[1139]: WARNING: Unable to find provider '' of required component 'dock' (mate-panel:1436): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (nm-applet:1473): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1547237/+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 1551277] Re: mate-power-manager crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1551277 Title: mate-power-manager crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() Status in glib2.0 package in Ubuntu: New Status in mate-power-manager package in Ubuntu: Confirmed Bug description: I experimented with the Cupertino panel layout and Plank when this error suddenly popped up. Power manager seems to have crashed and did not restart. Ubuntu 16.04 Daily release amd64 20160229 mate-power-manager: Installert: 1.12.1-1 Kandidat: 1.12.1-1 Versjonstabell: *** 1.12.1-1 500 500 http://no.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-power-manager 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Mon Feb 29 16:20:24 2016 ExecutablePath: /usr/bin/mate-power-manager InstallationDate: Installed on 2016-02-29 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160229) ProcCmdline: mate-power-manager SegvAnalysis: Segfault happened at: 0x7fadf5140e69 : mov(%rbx),%rdi PC (0x7fadf5140e69) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-power-manager StacktraceTop: up_exported_daemon_get_lid_is_closed () from /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 ?? () g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-power-manager crashed with SIGSEGV in up_exported_daemon_get_lid_is_closed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: mate-session[1023]: WARNING: Unable to find provider '' of required component 'dock' (nm-applet:1424): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed (mate-power-manager:1402): libupower-glib-WARNING **: Couldn't connect to proxy: Feil ved kall til StartServiceByName for org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.UPower': timed out (mate-panel:1377): EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion 'global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1551277/+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 1555455] Re: mate-power-manager crashed with SIGSEGV in hide_timeout()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1555455 Title: mate-power-manager crashed with SIGSEGV in hide_timeout() Status in glib2.0 package in Ubuntu: New Status in mate-power-manager package in Ubuntu: Confirmed Bug description: mate-power-manager seemingly randomly crashes and the icon in the panel vanishes until I reboot (probably logout + login would also suffice I guess) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-power-manager 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Wed Mar 9 22:31:58 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/mate-power-manager InstallationDate: Installed on 2016-03-06 (3 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-power-manager SegvAnalysis: Segfault happened at: 0x415c30: testb $0x1,0x0(%rbp) PC (0x00415c30) ok source "$0x1" ok destination "0x0(%rbp)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-power-manager StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-power-manager crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: mate-session[1467]: WARNING: Unable to find provider '' of required component 'dock' (nm-applet:2016): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed (mate-power-manager:1968): Gdk-CRITICAL **: IA__gdk_window_thaw_toplevel_updates_libgtk_only: assertion 'private->update_and_descendants_freeze_count > 0' failed (blueman-applet:1978): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1555455/+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 1567922] Re: mate-panel crashed with SIGSEGV in g_pattern_match()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1567922 Title: mate-panel crashed with SIGSEGV in g_pattern_match() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: Got this error, when restarted the system after partial upgrading. Nothing seems to be broken, even though it says that something crashed. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Fri Apr 8 15:34:34 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-03-24 (14 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f071a852849 : cmp %esi,0x8(%rdi) PC (0x7f071a852849) ok source "%esi" ok destination "0x8(%rdi)" (0x000f) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_pattern_match () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 gtk_rc_get_style () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_pattern_match() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1567922/+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 1708047] Re: mate-panel crashed with SIGSEGV in mate_panel_applet_can_freely_move()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1708047 Title: mate-panel crashed with SIGSEGV in mate_panel_applet_can_freely_move() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: Well I dont know exactly, but its an automatically generated report, so i am sending it. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-panel 1.18.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: MATE Date: Tue Aug 1 23:09:01 2017 ExecutablePath: /usr/bin/mate-panel LiveMediaBuild: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170725.1) ProcCmdline: mate-panel ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55e2b3cfab78 : mov0x38(%rbx),%rdi PC (0x55e2b3cfab78) ok source "0x38(%rbx)" (0x0038) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: mate_panel_applet_can_freely_move () mate_panel_applet_frame_sync_menu_state () _mate_panel_applet_frame_activated () ?? () g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: mate-panel crashed with SIGSEGV in mate_panel_applet_can_freely_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1708047/+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 1725631] Re: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width()
** Also affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1725631 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() Status in gdk-pixbuf package in Ubuntu: New Status in mate-dock-applet package in Ubuntu: Confirmed Bug description: I had just installed Planner 0.14.6 and attempting to move the dock icon which disappeared and the crash occurred. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-dock-applet 0.79-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Sat Oct 21 11:37:17 2017 ExecutablePath: /usr/lib/mate-applets/mate-dock-applet/dock_applet.py InstallationDate: Installed on 2017-09-29 (21 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170926) InterpreterPath: /usr/bin/python3.6 ProcCmdline: python3 /usr/lib/mate-applets/mate-dock-applet/dock_applet.py ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fb63b6d5246 : cmp %rax,(%rdx) PC (0x7fb63b6d5246) ok source "%rax" ok destination "(%rdx)" (0x7fb63dd4ff3abb49) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-dock-applet StacktraceTop: gdk_pixbuf_get_width () from /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: dock_applet.py crashed with SIGSEGV in gdk_pixbuf_get_width() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1725631/+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 1678634] Re: mate-panel crashed with SIGSEGV in setup_button()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1678634 Title: mate-panel crashed with SIGSEGV in setup_button() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: When doing update of the program starter icon, it did not change. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-panel 1.18.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 2 17:30:24 2017 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2017-03-29 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) ProcCmdline: mate-panel ProcEnviron: LANGUAGE=sv_SE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x55685325c54c:mov(%rax),%rbx PC (0x55685325c54c) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rbx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm backup bin cdrom dip disk libvirt lpadmin mail plugdev root sambashare sudo sys www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1678634/+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 1527352] Re: marco crashed with SIGSEGV in XMoveResizeWindow()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1527352 Title: marco crashed with SIGSEGV in XMoveResizeWindow() Status in glib2.0 package in Ubuntu: New Status in marco package in Ubuntu: New Bug description: resizing browser, several programs open for some hours without problems before ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: marco 1.10.2-1 ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6 Uname: Linux 4.2.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Thu Dec 17 19:12:41 2015 ExecutablePath: /usr/bin/marco ProcCmdline: /usr/bin/marco --replace ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6ac12097e0 : mov 0x968(%rdi),%rax PC (0x7f6ac12097e0) ok source "0x968(%rdi)" (0x0a19) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: marco StacktraceTop: XMoveResizeWindow () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: marco crashed with SIGSEGV in XMoveResizeWindow() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lp lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1527352/+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 1550924] Re: mate-panel crashed with SIGSEGV in gtk_rc_styles_hash()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1550924 Title: mate-panel crashed with SIGSEGV in gtk_rc_styles_hash() Status in glib2.0 package in Ubuntu: New Status in gtk+2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: Mate-panel disappeared after installing Wine & some windows softwares (Adobe Illustrator CS) ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Sun Feb 28 20:46:04 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-27 (1 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f8bd9774575:add(%rdi),%edx PC (0x7f8bd9774575) ok source "(%rdi)" (0x9001f) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_modify_style () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1550924/+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 1505884] Re: caja crashed with SIGSEGV in caja_icon_container_search_entry_flush_timeout()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1505884 Title: caja crashed with SIGSEGV in caja_icon_container_search_entry_flush_timeout() Status in caja package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: New Bug description: Description: Ubuntu Wily Werewolf (development branch) Release: 15.10 caja: Installed: 1.10.4-1 Candidate: 1.10.4-1 Version table: *** 1.10.4-1 0 500 http://ftp.sjtu.edu.cn/ubuntu/ wily/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: caja 1.10.4-1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Wed Oct 14 11:12:27 2015 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 ExecutablePath: /usr/bin/caja InstallationDate: Installed on 2014-06-03 (497 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 ProcCmdline: caja ProcEnviron: LANGUAGE=zh_CN: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=zh_CN.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x4f921e: mov0x298(%rax),%rdi PC (0x004f921e) ok source "0x298(%rax)" (0x0298) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: caja StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: caja crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: Upgraded to wily on 2015-09-24 (19 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1505884/+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 1539251] Re: crash after panel_profile_background_change_notify
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1539251 Title: crash after panel_profile_background_change_notify Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: The Mate panel in Ubuntu 16.04 LTS Mate alpha1 is a bit buggy. 1. Selecting the plugin Advanced Mate menu does not work (There is also no icon shown when selecting this menu in the panel) -When the Advanced Mate menu is added to the panel just a fullstop is shown on the panel, which can't be removed afterwards. 2. Changing the Mate panel layout with the Mate tweak application causes SIGSEGV -I tried changing to opensuse layout -> SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.1-1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 28 21:12:44 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-01-22 (6 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160103) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x4567dd : cmp (%rdx),%rax PC (0x004567dd) ok source "(%rdx)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: panel_frame_set_edges () panel_toplevel_update_edges () ?? () g_cclosure_marshal_VOID__STRINGv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: mate-panel crashed with SIGSEGV in panel_frame_set_edges() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1539251/+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 1560729] Re: tracker-extract crashed with SIGSEGV in free()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1560729 Title: tracker-extract crashed with SIGSEGV in free() Status in bugtimetracker package in Ubuntu: New Status in glib2.0 package in Ubuntu: New Status in tracker package in Ubuntu: New Bug description: # sudo rm -r /var/lib/apt/lists/* -vf removido '/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_xenial_InRelease' removido '/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_xenial_partner_binary-amd64_Packages' removido '/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_xenial_partner_binary-i386_Packages' removido '/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_xenial_partner_i18n_Translation-en' removido '/var/lib/apt/lists/archive.canonical.com_ubuntu_dists_xenial_partner_source_Sources' removido '/var/lib/apt/lists/br.archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease' removido '/var/lib/ ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: tracker-extract 1.6.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 22 19:49:51 2016 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2016-03-22 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: /usr/lib/tracker/tracker-extract SegvAnalysis: Segfault happened at: 0x7f004bf2fbc2 : mov-0x8(%rdi),%rax PC (0x7f004bf2fbc2) ok source "-0x8(%rdi)" (0xac43fffa) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: tracker StacktraceTop: free () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gst_discoverer_stream_info_list_free () from /usr/lib/x86_64-linux-gnu/libgstpbutils-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/tracker-1.0/extract-modules/libextract-gstreamer.so Title: tracker-extract crashed with SIGSEGV in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bugtimetracker/+bug/1560729/+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 1563782] Re: mate-panel crashed with SIGSEGV in strlen()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1563782 Title: mate-panel crashed with SIGSEGV in strlen() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: Restarted Caja because Dropbox requested it. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 30 11:39:15 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-01-05 (85 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: mate-panel --sm-client-id 105e6b402b2e025a4114593265199299750021140050 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/fish SegvAnalysis: Segfault happened at: 0x7f6a54733f44 : pcmpeqb (%rax),%xmm0 PC (0x7f6a54733f44) ok source "(%rax)" (0xffc0) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:137 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 gtk_rc_get_style () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in strlen() UpgradeStatus: Upgraded to xenial on 2016-03-30 (0 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1563782/+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 1568438] Re: mate-panel crashed with SIGSEGV in g_slist_copy_deep()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1568438 Title: mate-panel crashed with SIGSEGV in g_slist_copy_deep() Status in glib2.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: Confirmed Bug description: ubuntu-mate 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:17:28 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.371 CurrentDesktop: MATE Date: Sun Apr 10 08:10:32 2016 ExecutablePath: /usr/bin/mate-panel LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160408) ProcCmdline: mate-panel ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f1772835cbf :mov (%rbx),%rax PC (0x7f1772835cbf) ok source "(%rbx)" (0x646e69762074796e) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 gtk_rc_get_style () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_copy_deep() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1568438/+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 1568253] Re: mate-power-manager crashed with SIGSEGV in malloc_consolidate()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1568253 Title: mate-power-manager crashed with SIGSEGV in malloc_consolidate() Status in glib2.0 package in Ubuntu: New Status in mate-power-manager package in Ubuntu: New Bug description: I wascreating desktop shortcuts from steam, while downloading Team Fortress 2 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-power-manager 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Sat Apr 9 06:17:01 2016 ExecutablePath: /usr/bin/mate-power-manager InstallationDate: Installed on 2016-04-09 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) ProcCmdline: mate-power-manager ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f114eff8738:mov0x8(%rbx),%rax PC (0x7f114eff8738) ok source "0x8(%rbx)" (0x10002728f08) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-power-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 free () from /lib/x86_64-linux-gnu/libc.so.6 g_hash_table_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_hash_table_destroy () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-power-manager crashed with SIGSEGV in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: mate-session[1905]: WARNING: Unable to find provider '' of required component 'dock' (nm-applet:2331): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed (blueman-applet:2311): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates: assertion 'window->update_and_descendants_freeze_count > 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1568253/+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 1671885] Re: synapse crashed with SIGSEGV in __GI___libc_free()
** Also affects: libzeitgeist (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1671885 Title: synapse crashed with SIGSEGV in __GI___libc_free() Status in libzeitgeist package in Ubuntu: New Status in synapse package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: synapse 0.2.99.2-2 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 10 19:07:46 2017 ExecutablePath: /usr/bin/synapse InstallationDate: Installed on 2017-03-09 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: synapse ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fb4b2545162 <__GI___libc_free+34>: mov -0x8(%rdi),%rax PC (0x7fb4b2545162) ok source "-0x8(%rdi)" (0x3fb0101010101008) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: synapse StacktraceTop: __GI___libc_free (mem=0x3fb0101010101010) at malloc.c:2963 zeitgeist_symbol_info_register () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_initialize_symbols () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_symbol_get_all_children () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 zeitgeist_db_reader_get_where_clause_for_symbol () from /usr/lib/x86_64-linux-gnu/libzeitgeist-2.0.so.0 Title: synapse crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzeitgeist/+bug/1671885/+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 1756801] Re: mate-tweak crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1756801 Title: mate-tweak crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in glib2.0 package in Ubuntu: New Status in mate-tweak package in Ubuntu: Confirmed Bug description: Changing layouts between Pantheon and Traditional, mate-tweak closed itself. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: mate-tweak 18.04.14-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 18 22:56:45 2018 ExecutablePath: /usr/bin/mate-tweak InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: mate-tweak ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7fe750c20c31 : movzbl 0x14(%rdx),%eax PC (0x7fe750c20c31) ok source "0x14(%rdx)" (0x10014) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-tweak StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-tweak crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1756801/+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 1627278] Re: wingpanel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627278 Title: wingpanel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in Wingpanel: New Status in glib2.0 package in Ubuntu: New Bug description: wingpanel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() ProblemType: Crash DistroRelease: elementary 0.4 Package: wingpanel 2.0.1~r153-0+pkg29~daily~ubuntu0.4.1 [origin: LP-PPA-elementary-os-daily] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: wingpanel CurrentDesktop: Pantheon Date: Sat Sep 24 12:14:08 2016 ExecutablePath: /usr/bin/wingpanel GSettings: org.pantheon.desktop.wingpanel use-transparency true GsettingsChanges: InstallationDate: Installed on 2016-06-16 (99 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: wingpanel SegvAnalysis: Segfault happened at: 0x7f90c356f7e5 : mov(%rdi),%rax PC (0x7f90c356f7e5) ok source "(%rdi)" (0x020b5dc9) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: wingpanel StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libgee-0.8.so.2 Title: wingpanel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy libvirtd lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/wingpanel/+bug/1627278/+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 1726872] Re: mate-appearance-properties crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726872 Title: mate-appearance-properties crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in glib2.0 package in Ubuntu: Confirmed Status in mate-control-center package in Ubuntu: Confirmed Bug description: mate-appearance-properties crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-control-center 1.18.2-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Oct 25 00:34:26 2017 ExecutablePath: /usr/bin/mate-appearance-properties InstallationDate: Installed on 2017-10-24 (0 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: mate-appearance-properties ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f5220096d01 : movzbl 0x14(%rdx),%eax PC (0x7f5220096d01) ok source "0x14(%rdx)" (0x30014) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: mate-control-center StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: mate-appearance-properties crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1726872/+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 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
Same issue here in Trusty with Jamulus tooltips :
https://github.com/corrados/jamulus/issues/456
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1478173
Title:
Ambiance & Radiance themes are missing a "background-color" for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in One Hundred Papercuts:
Confirmed
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance & Radiance GTK3 themes.
They're missing a "background-color" for the .tooltip {...} CSS rule
in their config files. They have a "tooltip_bg_color" variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the ".tooltip" CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+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 1478173] Re: Ambiance & Radiance themes are missing a "background-color" for tooltip elements (needed for GTK3-enabled Firefox Nightly)
Same issue here with Jamulus tooltips :
https://github.com/corrados/jamulus/issues/456
** Bug watch added: github.com/corrados/jamulus/issues #456
https://github.com/corrados/jamulus/issues/456
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1478173
Title:
Ambiance & Radiance themes are missing a "background-color" for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in One Hundred Papercuts:
Confirmed
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance & Radiance GTK3 themes.
They're missing a "background-color" for the .tooltip {...} CSS rule
in their config files. They have a "tooltip_bg_color" variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the ".tooltip" CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1478173/+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
