[Bug 1278437] Re: can't move link type .desktop files around on desktop

2016-09-18 Thread dash
Just upgraded to 16.04 LTS and a desktop URL link icon can't be dragged around. When trying to drag such an icon, where it would be dropped appears a copy of the webpage referred to. WHY DO YOU HAVE TO SUCK SO MUCH? WHY IS INCOMPETENCE THE NORM? -- You received this bug notification because you

[Bug 1671425] [NEW] Syslog full of error 0x6 /home/bob/foo/rxtx-devel/build/../src/termios.c(869): Descripteur invalide.

2017-03-09 Thread Dash
Public bug reported: Hello, syslog is full of this error, around each 5 seconds Mar 9 11:40:23 localhost gnome-session[2163]: Error 0x6 at /home/bob/foo/rxtx-devel/build/../src/termios.c(869): Descripteur invalide. Mar 9 11:40:23 localhost gnome-session[2163]: #015 Mar 9 11:40:23 localhost

[Bug 1790870] Re: No X display - gdm3 crash with segfault

2018-09-06 Thread Dash
Hi Daniel, I found 2 files: /var/crash/_usr_bin_gnome-shell.124.crash and /var/crash/_usr_bin_Xwayland.124.crash that I sended them with ubuntu- bug but after this I never got new bugs ID :( Two new files appeard with extension .upload and they are empty. There is also a .lock file in this

[Bug 1790870] Re: No X display - gdm3 crash with segfault

2018-09-06 Thread Dash
I tried point 2. Here are the links: >From 18.04 version https://errors.ubuntu.com/oops/c20dade6-b1a0-11e8-8fa5-fa163ee63de6 https://errors.ubuntu.com/oops/da31709a-b19f-11e8-8fa5-fa163ee63de6 >From 16.04 version https://errors.ubuntu.com/oops/01680142-9cae-11e8-b517-fa163e0ec2f1

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

2018-09-06 Thread Dash
I ran lsof, max display lines I saw (sudo lsof |wc -l) are near of 22000. Attached is an lsof runned after I restart gdm3 Daniel ** Attachment added: "lsof_1597150.log" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1597150/+attachment/5185622/+files/lsof_1597150.log -- You received

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

2018-09-07 Thread Dash
Hi, here is the detail of what happend: - remove all files from /var/crash - restart computer, the Ubuntu screen with the dots is shown - when time of greeting appears in /var/crash _usr_bin_Xwayland.124.crash and .lock files - some seconds after appears _usr_bin_gnome-shell.124.crash in this

[Bug 1790870] Re: No X display - gdm3 crash with segfault

2018-09-06 Thread Dash
*** This bug is a duplicate of bug 1791023 *** https://bugs.launchpad.net/bugs/1791023 Bug #1791023 is the crash report after having applied the workaround. It's now against gdm3. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 1597150] Re: gdm3 crashed with SIGTRAP logging "Creating pipes for GWakeup: Too many open files\n" in g_wakeup_new() from g_main_context_new() from g_dbus_connection_send_message_with_reply_sync(

2018-09-07 Thread Dash
I did the all stuff again and first crashed gnome-shell then Xwayland. gdm3 is still running with the same PID but gdm-wayland-session PID change after few seconds. Example: 821 ?Ssl0:00 /usr/sbin/gdm3 3911 pts/3S+ 0:00 grep --color=auto gdm3 3935 tty1 Ssl+ 0:00

[Bug 1801747] Re: External display not recognized, internal one goes to black

2018-11-06 Thread Dash
Ubuntu 18.10 does have the same problem, Ubuntu 16.04.2 has *NO* problem. From where could I get an 4.4 kernel for 18.04 for testing purpose ? Other infos: when I check in systems, it show me 3 display despite the fact that only 2 are connected: 1. internal display 2. unknown display with

[Bug 1801747] Re: External display not recognized, internal one goes to black

2018-11-07 Thread Dash
More infos. I installed the notebook from scratch with a 16.04.2 image and update to latest 16.04 packages which installed 4.15.0-38 kernel. The laptop has the correct behavior, without entering settings I can switch/duplicate displays with the fn key. So original problem seems not related to

[Bug 1860761] [NEW] Dell XPS 13 - Bios upgrade not working - Always ask for power supply

2020-01-24 Thread Dash
Public bug reported: Each time the notebook starts I'm advised that a new bios upgrade is out: XPS 13 7390 System Update 0.1.3.1 => 0.1.4.0 Problem is that when I ask for update, I always get this message (traduction from french): Not possible to upgrade "XPS 13 7390 System Update": connect

[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

2020-01-28 Thread Dash
Hi Sebastien. While rebooting to have a clear journalctl output to send you, the updates work and I found why. Battery has to be 100% charged. While still on power, reboot the machine, do the upgrade, reboot and finally the BIOS gets upgraded. After last reboot you can remove the power supply.

[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

2020-01-30 Thread Dash
Well, have to wait for next bios update. If it help, attached you will find upower when discharging and charging, around 15 seconds between the 2 output ** Attachment added: "upower.txt"

[Bug 1860761] Re: Dell XPS 13 - Bios upgrade not working - Always ask for power supply

2020-03-31 Thread Dash
A bios update is not always available in a 60 days time life! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1860761 Title: Dell XPS 13 - Bios upgrade not working - Always

[Bug 1898466] [NEW] workaround=all no more recognize using fuse in fstab

2020-10-04 Thread Dash
Public bug reported: In Ubuntu 18.04 we had this line in fstab which was working well sshfs#dh@keewin:Mes_documents/ /home/dh/Mes_documents/ fuse compression=yes,port=36022,user,,noatime,reconnect,workaround=all 0 0 After upgrade to 20.04 we get dh@feijoa:~$ mount /home/dh/Mes_documents/

[Bug 1856388] Re: Toolbox dialog is too tall on a normal laptop screen and makes Gimp useless

2020-11-18 Thread Dash
Same problem on Ubuntu 20.04.1. Notebook 4K, external screen 4K, imagine what we see ! :( We tried personalsize, auto define from system, no luck ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1856388/+attachment/5435773/+files/gimp%20toolbox.png --

[Bug 1852179] Re: Keyboard not working in GIMP 2.10.8 / Ubuntu 19.04

2020-11-18 Thread Dash
Shortcuts are still not working on Ubuntu 20.04.1 Gimp 2.10.18. Alt shows underlined character but nothing happend. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1852179 Title:

[Bug 436713] Re: Movie Player closes automatically on opening a video file.

2009-09-25 Thread Laya Dash
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/32438519/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/32438520/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/32438521/ProcStatus.txt -- Movie

[Bug 436713] [NEW] Movie Player closes automatically on opening a video file.

2009-09-25 Thread Laya Dash
Public bug reported: Binary package hint: totem I opened a .vob file and the window closed by itself without showing any error or asking for updates. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5

[Bug 994866] [NEW] package shared-mime-info 1.0-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2012-05-04 Thread Dash Runner
Public bug reported: updates are creating issues...this is my second installation of Precise within 24hrs because of slow connection and updates fouling menus, panels, graphics, timing...HP g7 w/AMD quad-core 7 graphics and max 8G of RAM. ProblemType: Package DistroRelease: Ubuntu 12.04

[Bug 994866] Re: package shared-mime-info 1.0-0ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2012-05-04 Thread Dash Runner
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/994866 Title: package shared-mime-info 1.0-0ubuntu4 failed to install/upgrade: subprocess installed post-installation

[Bug 933115] [NEW] evince doesn't open PDFs when using right-click Open nor Open with...

2012-02-15 Thread Dash Runner
Public bug reported: To open PDFs I must start Evince from menu (after re-enabling menu's listing for it) and then open any PDFs through File... in menu. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: evince 2.32.0-0ubuntu12.4 ProcVersionSignature: Ubuntu 2.6.38-13.55-generic 2.6.38.8

[Bug 933115] Re: evince doesn't open PDFs when using right-click Open nor Open with...

2012-02-15 Thread Dash Runner
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/933115 Title: evince doesn't open PDFs when using right-click Open nor Open with... To manage notifications about this bug go to:

[Bug 933115] Re: evince doesn't open PDFs when using right-click Open nor Open with...

2012-03-05 Thread Dash Runner
I am no longer working in this installation of Ubuntu that had the bug. It was reported as a factual bug in that I could find no reason why PDFs, connected by extension to open in Evince, were not being opened unless I started Evince and opened them with File:Open.I tried disassociating